Secure transactions with offline device

ABSTRACT

A method being implemented via execution of computing instructions configured to run at one or more processors and stored at one or more non-transitory computer-readable media. The method can include receiving a transaction amount and a preauthorization code from a first entity. The preauthorization code can include a preauthorization amount, an expiration time, and a digital signature. The transaction amount is for a transaction authorized by a user of a mobile device at a point-of-sale terminal of the first entity. The transaction amount is less than or equal to the preauthorization amount. The mobile device received the preauthorization code and stored the preauthorization code in the mobile device while the mobile device was in data communication with a mobile wallet provider. The mobile device provided a transaction code to the point-of-sale terminal while the mobile device was unable to communicate with the mobile wallet provider. The transaction code includes the preauthorization code, a transaction identifier for the transaction, and the transaction amount. The method also can include verifying the preauthorization code using the digital signature of the preauthorization code. The method additionally can include sending an approval for the transaction to the first entity in real-time while the user remains at the point-of-sale terminal of the first entity. Other embodiments are described.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. patent applicationSer. No. 15/873,549, filed Jan. 17, 2018; U.S. patent application Ser.No. 15/873,533, filed Jan. 17, 2018; U.S. patent application Ser. No.15/873,508, filed Jan. 17, 2018; U.S. patent application Ser. No.15/873,481, filed Jan. 17, 2018; U.S. patent application Ser. No.15/873,463, filed Jan. 17, 2018; and U.S. patent application Ser. No.15/873,440, filed Jan. 17, 2018. U.S. patent application Ser. Nos.15/873,549, 15/873,533, 15/873,508, 15/873,481, 15/873,463, and15/873,440 are each a continuation-in-part of U.S. patent applicationSer. No. 15/170,781, filed Jun. 1, 2016, which is a continuation of U.S.patent application Ser. No. 14/805,214, filed Jul. 21, 2015. Thisapplication also claims the benefit of U.S. Provisional Application No.62/779,987, filed Dec. 14, 2018. U.S. Provisional Application No.62/779,987 and U.S. patent application Nos. 15/873,549, 15/873,533,15/873,508, 15/873,481, 15/873,463, 15/873,440, 15/170,781, and14/805,214 are incorporated herein by reference in their entirety.

TECHNICAL FIELD

This disclosure relates generally to secure processing of transactions,and relates more particularly to providing secure transactions withoffline devices.

BACKGROUND

In a typical transaction involving a mobile device, a mobile walletapplication in the mobile device generally needs to communicate (e.g.,through the Internet) with a mobile wallet provider during thetransaction, such as to initiate the transaction and/or to authorize thetransaction. When the mobile device is unable access the mobile walletprovider, such as due to the mobile device being unable to access theInternet, the transaction generally cannot proceed.

BRIEF DESCRIPTION OF THE DRAWINGS

To facilitate further description of the embodiments, the followingdrawings are provided in which:

FIG. 1 illustrates a block diagram of a system that can be employed fora secure real-time payment transaction network, according to anembodiment;

FIG. 2 illustrates a flow chart for a method, according to anembodiment;

FIG. 3 illustrates a flow chart for a method, according to anotherembodiment;

FIG. 4 illustrates a flow chart for a method, according to anotherembodiment;

FIG. 5 illustrates a flow chart for a method, according to anotherembodiment;

FIG. 6 illustrates a flow chart for a method, according to anotherembodiment;

FIG. 7 illustrates a computer that is suitable for implementing anembodiment of components of the system of FIG. 1;

FIG. 8 illustrates a representative block diagram of an example ofelements included in circuit boards inside a chassis of the computer ofFIG. 7;

FIG. 9 illustrates a flow chart for a method, according to anotherembodiment;

FIG. 10 illustrates a flow chart for a method, according to anotherembodiment;

FIG. 11 illustrates a flow chart for a method, according to anotherembodiment;

FIG. 12 illustrates a flow chart for a method, according to anotherembodiment;

FIG. 13 illustrates a flow chart for a method, according to anotherembodiment;

FIG. 14 illustrates a flow chart for a method, according to anotherembodiment;

FIG. 15 illustrates a flow chart for a method, according to anotherembodiment;

FIG. 16 illustrates a flow chart for a method, according to anotherembodiment;

FIG. 17 illustrates an exemplary user interface display to allow theconsumer of FIG. 1 to approve a transaction on the mobile device of FIG.1;

FIG. 18 illustrates an exemplary user interface display to allow theconsumer of FIG. 1 to choose to use another account for the paymenttransaction when the approved account has insufficient funds or limitedfunds;

FIG. 19 illustrates an exemplary user interface display to allow theconsumer of FIG. 1 to select another account for the payment transactionwhen the approved account has insufficient funds;

FIG. 20 illustrates an exemplary user interface display to allow theconsumer of FIG. 1 to select the amount to pay using the other accountselected the user interface display of FIG. 19;

FIG. 21 illustrates an exemplary user interface display to confirm thata payment request has been sent from the mobile device of FIG. 1;

FIG. 22 illustrates an exemplary user interface display to confirm thatthe payment transaction to the merchant of FIG. 1 has successfullycompleted;

FIG. 23 illustrates a flow chart for a method, according to anotherembodiment;

FIG. 24 illustrates a flow chart for a method, according to anotherembodiment;

FIG. 25 illustrates a flow chart for a method, according to anotherembodiment;

FIG. 26 illustrates a flow chart for a method, according to anotherembodiment;

FIG. 27 illustrates a flow chart for a method, according to anotherembodiment; and

FIG. 28 illustrates a flow chart for a method, according to anotherembodiment.

For simplicity and clarity of illustration, the drawing figuresillustrate the general manner of construction, and descriptions anddetails of well-known features and techniques may be omitted to avoidunnecessarily obscuring the present disclosure. Additionally, elementsin the drawing figures are not necessarily drawn to scale. For example,the dimensions of some of the elements in the figures may be exaggeratedrelative to other elements to help improve understanding of embodimentsof the present disclosure. The same reference numerals in differentfigures denote the same elements.

The terms “first,” “second,” “third,” “fourth,” and the like in thedescription and in the claims, if any, are used for distinguishingbetween similar elements and not necessarily for describing a particularsequential or chronological order. It is to be understood that the termsso used are interchangeable under appropriate circumstances such thatthe embodiments described herein are, for example, capable of operationin sequences other than those illustrated or otherwise described herein.Furthermore, the terms “include,” and “have,” and any variationsthereof, are intended to cover a non-exclusive inclusion, such that aprocess, method, system, article, device, or apparatus that comprises alist of elements is not necessarily limited to those elements, but mayinclude other elements not expressly listed or inherent to such process,method, system, article, device, or apparatus.

The terms “left,” “right,” “front,” “back,” “top,” “bottom,” “over,”“under,” and the like in the description and in the claims, if any, areused for descriptive purposes and not necessarily for describingpermanent relative positions. It is to be understood that the terms soused are interchangeable under appropriate circumstances such that theembodiments of the apparatus, methods, and/or articles of manufacturedescribed herein are, for example, capable of operation in otherorientations than those illustrated or otherwise described herein.

The terms “couple,” “coupled,” “couples,” “coupling,” and the likeshould be broadly understood and refer to connecting two or moreelements mechanically and/or otherwise. Two or more electrical elementsmay be electrically coupled together, but not be mechanically orotherwise coupled together. Coupling may be for any length of time,e.g., permanent or semi-permanent or only for an instant. “Electricalcoupling” and the like should be broadly understood and includeelectrical coupling of all types. The absence of the word “removably,”“removable,” and the like near the word “coupled,” and the like does notmean that the coupling, etc. in question is or is not removable.

As defined herein, two or more elements are “integral” if they arecomprised of the same piece of material. As defined herein, two or moreelements are “non-integral” if each is comprised of a different piece ofmaterial.

As defined herein, “approximately” can, in some embodiments, mean withinplus or minus ten percent of the stated value. In other embodiments,“approximately” can mean within plus or minus five percent of the statedvalue. In further embodiments, “approximately” can mean within plus orminus three percent of the stated value. In yet other embodiments,“approximately” can mean within plus or minus one percent of the statedvalue.

As defined herein, “real-time” can, in some embodiments, be defined withrespect to operations carried out as soon as practically possible uponoccurrence of a triggering event. A triggering event can include receiptof data necessary to execute a task or to otherwise process information.Because of delays inherent in transmission and/or in computing speeds,the term “real time” encompasses operations that occur in “near” realtime or somewhat delayed from a triggering event. In a number ofembodiments, “real time” can mean real time less a time delay forprocessing (e.g., determining) and/or transmitting data. The particulartime delay can vary depending on the type and/or amount of the data, theprocessing speeds of the hardware, the transmission capability of thecommunication hardware, the transmission distance, etc. However, in manyembodiments, the time delay can be less than approximately one second,five seconds, ten seconds, thirty seconds, one minute, or five minutes.

DESCRIPTION OF EXAMPLES OF EMBODIMENTS

Various embodiments include a system including one or more processingmodules and one or more non-transitory memory storage modules storingcomputing instructions configured to run on the one or more processingmodules and perform certain acts. The acts can include receiving, at afirst financial institution from a mobile device of a consumer, a firstrequest to pay a merchant for a payment amount from a first account ofthe consumer maintained by the first financial institution. The firstrequest can include first information including a merchant identifier, atransaction identifier, and the payment amount. The first informationcan be sent to the first financial institution from a mobile applicationrunning on a mobile device used by the consumer at a store of themerchant to pay for one or more items to be purchased from the merchantby the consumer for the payment amount. The merchant identifier can beassociated with the merchant. The mobile application can be associatedwith the first account. The acts also can include determining, at thefirst financial institution, second information including an accountidentifier of a second account of the merchant maintained by a secondfinancial institution, at least partially based on the merchantidentifier and third information obtained from a first system. The firstsystem can be in data communication with the first financial institutionand the second financial institution. The first system can be maintainedby an entity that is different from the first financial institution andthe second financial institution. The acts additionally can includeauthorizing, at the first financial institution, a payment from thefirst account to the second account. The acts further can includesending, from the first financial institution to the first system,payment information regarding a payment to be made to the second accountfrom the first account. The payment information can be routed throughthe first system to the second financial institution such that thesecond financial institution, upon receiving the payment information,notifies the merchant to satisfy an expectation of the merchant forpayment from the consumer. The payment information can include thetransaction identifier, the account identifier of the second account,and the payment amount.

A number of embodiments include a method being implemented via one ormore processing modules and one or more non-transitory memory storagemodules storing computing instructions configured to run on the one ormore processing modules. The method can include receiving, at a firstfinancial institution from a mobile device of a consumer, a firstrequest to pay a merchant for a payment amount from a first account ofthe consumer maintained by the first financial institution. The firstrequest can include first information including a merchant identifier, atransaction identifier, and the payment amount. The first informationcan be sent to the first financial institution from a mobile applicationrunning on a mobile device used by the consumer at a store of themerchant to pay for one or more items to be purchased from the merchantby the consumer for the payment amount. The merchant identifier can beassociated with the merchant. The mobile application can be associatedwith the first account. The method also can include determining, at thefirst financial institution, second information including an accountidentifier of a second account of the merchant maintained by a secondfinancial institution, at least partially based on the merchantidentifier and third information obtained from a first system. The firstsystem can be in data communication with the first financial institutionand the second financial institution. The first system can be maintainedby an entity that is different from the first financial institution andthe second financial institution. The method additionally can includeauthorizing, at the first financial institution, a payment from thefirst account to the second account. The method further can includesending, from the first financial institution to the first system,payment information regarding a payment to be made to the second accountfrom the first account. The payment information can be routed throughthe first system to the second financial institution such that thesecond financial institution, upon receiving the payment information,notifies the merchant to satisfy an expectation of the merchant forpayment from the consumer. The payment information can include thetransaction identifier, the account identifier of the second account,and the payment amount.

Additional embodiments include a system including one or more processingmodules and one or more non-transitory memory storage modules storingcomputing instructions configured to run on the one or more processingmodules and perform certain acts. The acts can include receiving, at afirst system from a first entity, a request including a merchantidentifier. The merchant identifier can be associated with a merchant.The first system can be in data communication with a first financialinstitution and a second financial institution. The first system can bemaintained by an entity that is different from the first financialinstitution and the second financial institution. The first financialinstitution can maintain a first account of a consumer. The first systemcan be in data communication with a merchant account database. The actsalso can include determining, at the first system, using the merchantaccount database, first information including an account identifier of asecond account of the merchant maintained by a second financialinstitution. The account identifier can be associated with the merchantidentifier in the merchant account database. The acts additionally caninclude sending the first information from the first system to the firstfinancial institution. The acts further can include receiving, at thefirst system from the first financial institution, payment informationregarding a payment to be made to the second account from the firstaccount to pay the merchant for one or more items to be purchased fromthe merchant by the consumer for the payment amount. The consumer canuse a mobile device at a store of the merchant to pay for the one ormore items. The mobile device can run a mobile application associatedwith the first account. The payment information can include atransaction identifier, the account identifier of the second account,and the payment amount. The acts additionally can include sending, fromthe first system to the second financial institution, the paymentinformation such that the second financial institution, upon receivingthe payment information, notifies the merchant to satisfy an expectationof the merchant for payment from the consumer.

Further embodiments include a method being implemented via one or moreprocessing modules and one or more non-transitory memory storage modulesstoring computing instructions configured to run on the one or moreprocessing modules. The method can include receiving, at a first systemfrom a first entity, a request including a merchant identifier. Themerchant identifier can be associated with a merchant. The first systemcan be in data communication with a first financial institution and asecond financial institution. The first system can be maintained by anentity that is different from the first financial institution and thesecond financial institution. The first financial institution canmaintain a first account of a consumer. The first system can be in datacommunication with a merchant account database. The method also caninclude determining, at the first system, using the merchant accountdatabase, first information including an account identifier of a secondaccount of the merchant maintained by a second financial institution.The account identifier can be associated with the merchant identifier inthe merchant account database. The method additionally can includesending the first information from the first system to the firstfinancial institution. The method further can include receiving, at thefirst system from the first financial institution, payment informationregarding a payment to be made to the second account from the firstaccount to pay the merchant for one or more items to be purchased fromthe merchant by the consumer for the payment amount. The consumer canuse a mobile device at a store of the merchant to pay for the one ormore items. The mobile device can run a mobile application associatedwith the first account. The payment information can include atransaction identifier, the account identifier of the second account,and the payment amount. The method additionally can include sending,from the first system to the second financial institution, the paymentinformation such that the second financial institution, upon receivingthe payment information, notifies the merchant to satisfy an expectationof the merchant for payment from the consumer.

Still further embodiments include one or more non-transitory memorystorage units including computer instructions that, when executed by oneor more processors, perform various acts. The acts can includereceiving, at a first system from a first entity, a request including amerchant identifier. The merchant identifier can be associated with amerchant. The first system can be in data communication with a firstfinancial institution and a second financial institution. The firstsystem can be maintained by an entity that is different from the firstfinancial institution and the second financial institution. The firstfinancial institution can maintain a first account of a consumer. Thefirst system can be in data communication with a merchant accountdatabase. The acts also can include determining, at the first system,using the merchant account database, first information including anaccount identifier of a second account of the merchant maintained by asecond financial institution. The account identifier can be associatedwith the merchant identifier in the merchant account database. The actsadditionally can include sending the first information from the firstsystem to the first financial institution. The acts further can includereceiving, at the first system from the first financial institution,payment information regarding a payment to be made to the second accountfrom the first account to pay the merchant for one or more items to bepurchased from the merchant by the consumer for the payment amount. Theconsumer can use a mobile device at a store of the merchant to pay forthe one or more items. The mobile device can run a mobile applicationassociated with the first account. The payment information can include atransaction identifier, the account identifier of the second account,and the payment amount. The acts additionally can include sending, fromthe first system to the second financial institution, the paymentinformation such that the second financial institution, upon receivingthe payment information, notifies the merchant to satisfy an expectationof the merchant for payment from the consumer.

Additional embodiments include a method being implemented via one ormore processing modules and one or more non-transitory memory storagemodules storing computing instructions configured to run on the one ormore processing modules. The method can include performing, at a mobiledevice, a preliminary identity authentication of a consumer using themobile device. The method also can include receiving at the mobiledevice first information from a point-of-sale terminal. The firstinformation can include a merchant identifier, a transaction identifier,and a payment amount. The merchant identifier can uniquely correspond tothe point-of-sale terminal at a store of a merchant. The mobile devicecan run a mobile application that is associated with a first account ofthe consumer using the mobile device. The first account of the consumercan be maintained by a first financial institution. The method furthercan include sending, from the mobile device to the first financialinstitution, a first request to pay the merchant for the payment amountfrom the first account for one or more items to be purchased from themerchant by the consumer. The first request can include the firstinformation, such that the first financial institution, upon receivingthe first request, determines second information including an accountidentifier of a second account of the merchant maintained by a secondfinancial institution, at least partially based on the merchantidentifier and third information obtained from a first system, and suchthat the first financial institution sends to the first system paymentinformation regarding a payment to be made to the second account fromthe first account. The payment information can be routed through thefirst system to the second financial institution such that the secondfinancial institution, upon receiving the payment information, cannotifies the merchant to satisfy an expectation of the merchant forpayment from the consumer. The first system can be in data communicationwith the first financial institution and the second financialinstitution. The first system can be maintained by an entity that isdifferent from the first financial institution and the second financialinstitution. The payment information can include the transactionidentifier, the account identifier of the second account, and thepayment amount. The payment information further can include one of: (a)a settlement credit push of funds for the payment amount from the firstaccount to the second account, or (b) an irrevocable promise to pay thepayment amount from the first account to the second account.

The method additionally can include, after sending the first request topay the merchant and before the payment information is sent to the firstsystem from the first financial institution: receiving, at the mobiledevice from the first financial institution, an additionalauthentication request to perform an additional identity authenticationof the consumer using the mobile device; performing, at the mobiledevice, the additional identity authentication of the consumer using themobile device; and sending, from the mobile device to the firstfinancial institution, a response to the additional authenticationrequest.

Performing the additional identity authentication of the consumer caninclude performing the additional authentication of the consumer basedat least in part on at least one of: determining biometrics of theconsumer using the mobile device; or requesting the consumer to enteradditional information in the mobile device.

The method further can include prior to sending the first request to paythe merchant: sending, from the mobile device to the first financialinstitution, a preliminary request for account information; andreceiving, at the mobile device from the first financial institution,the account information comprising an account balance and an accountstatus of the first account. The account information can include anaccount balance and an account status of the first account.

Further embodiments include a method being implemented via one or moreprocessing modules and one or more non-transitory memory storage modulesstoring computing instructions configured to run on the one or moreprocessing modules. The method can include determining, at apoint-of-sale terminal at a store of a merchant, a payment amount forone or more items to be purchased from the merchant by a consumer. Themethod also can include sending first information from the point-of-saleterminal to a mobile device used by the consumer. The first informationcan include a merchant identifier, a transaction identifier, and thepayment amount. The merchant identifier can uniquely correspond to thepoint-of-sale terminal at the store of the merchant. The mobile devicecan run a mobile application that is associated with a first account ofthe consumer using the mobile device. The first account of the consumercan be maintained by a first financial institution. The mobile device,upon receiving the first information, can send a first request to paythe merchant for the payment amount from the first account. The firstrequest can include the first information, such that the first financialinstitution, upon receiving the first request, determines secondinformation including an account identifier of a second account of themerchant maintained by a second financial institution, at leastpartially based on the merchant identifier and third informationobtained from a first system, and such that the first financialinstitution sends to the first system payment information regarding apayment to be made to the second account from the first account. Thepayment information can be routed through the first system to the secondfinancial institution. The first system can be in data communicationwith the first financial institution and the second financialinstitution. The first system can be maintained by an entity that isdifferent from the first financial institution and the second financialinstitution. The payment information can include the transactionidentifier, the account identifier of the second account, and thepayment amount. The payment information further can include one of: (a)a settlement credit push of funds for the payment amount from the firstaccount to the second account, or (b) an irrevocable promise to pay thepayment amount from the first account to the second account. The methodfurther can include receiving, at the point-of-sale terminal from thesecond financial institution, a notification to satisfy an expectationof the merchant for payment from the consumer.

Sending the first information from the point-of-sale terminal to themobile device can include sending the first information from thepoint-of-sale terminal to the mobile device using a proximity-basedwireless data communication protocol.

The method additionally can include receiving, at the point-of-saleterminal from the mobile device, information about the consumer.

Still further embodiments include a method being implemented via one ormore processing modules and one or more non-transitory memory storagemodules storing computing instructions configured to run on the one ormore processing modules. The method can include receiving, at a secondfinancial institution from a first system, payment information regardinga payment to be made to a second account of a merchant maintained by thesecond financial institution from a first account of a consumermaintained by a first financial institution to pay the merchant for oneor more items to be purchased from the merchant by the consumer for thepayment amount. The payment information can be sent from the firstfinancial institution to the first system and routed through the firstsystem to the second financial institution. The first system can be indata communication with the first financial institution and the secondfinancial institution. The first system can be maintained by an entitythat is different from the first financial institution and the secondfinancial institution. The consumer can use a mobile device at a storeof the merchant to pay for the one or more items. The mobile device canrun a mobile application associated with the first account. The paymentinformation can include a transaction identifier, an account identifierof the second account, and the payment amount. The first financialinstitution can determine the account identifier of the second accountbased on a merchant identifier and based on third information obtainedfrom the first system. The merchant identifier can uniquely correspondto a point-of-sale terminal at the store of a merchant. The mobiledevice can send a request to pay the merchant for the payment amountfrom the first account. The request can include first informationincluding the merchant identifier, a transaction identifier, and thepayment amount. The payment information further can include one of: (a)a settlement credit push of funds for the payment amount from the firstaccount to the second account, or (b) an irrevocable promise to pay thepayment amount from the first account to the second account. The methodalso can include sending, from the second financial institution to thepoint-of-sale terminal, a notification to satisfy an expectation of themerchant for payment from the consumer.

The method also can include, before sending the notification, creditingthe second account with the payment amount.

Sending the notification to satisfy the expectation of the merchant forpayment from the consumer can include notifying the merchant that fundsfor the payment amount are immediately available in the second account.

Additional embodiments include a system including one or more processorsand one or more non-transitory computer-readable media storing computinginstructions configured to run on the one more processors and performvarious acts. The acts can include determining, at a point-of-saleterminal at a store of a merchant, a payment amount for one or moreitems to be purchased from the merchant by a consumer in a transaction.The acts also can include generating a transaction code including amerchant public identifier, the payment amount, a transaction identifierfor the transaction, and a digital signature. The acts additionally caninclude providing the transaction code to a mobile device being used bythe consumer, such that the mobile device verifies the digital signatureand sends a request to pay the merchant for the payment amount from afirst account of the consumer maintained by a first financialinstitution, such that the first financial institution, upon receivingthe request to pay, retrieves from a transaction system an accountidentifier of a second account of the merchant maintained by a secondfinancial institution based on the merchant public identifier, and suchthat the first financial institution sends to the transaction systempayment information regarding a payment to be made to the second accountfrom the first account. The transaction system can be maintained by anentity that is different from the merchant, the first financialinstitution, and the second financial institution. The paymentinformation can be routed through the transaction system to the secondfinancial institution. The payment information can include thetransaction identifier, the account identifier of the second account,and the payment amount. The acts further can include receiving, at thepoint-of-sale terminal, a notification of payment for the transaction inreal-time while the consumer remains at the store of the merchant.

Further embodiments include a method being implemented via execution ofcomputing instructions configured to run at one or more processors andstored at one or more non-transitory computer-readable media. The methodcan include determining, at a point-of-sale terminal at a store of amerchant, a payment amount for one or more items to be purchased fromthe merchant by a consumer in a transaction. The method also can includegenerating a transaction code including a merchant public identifier,the payment amount, a transaction identifier for the transaction, and adigital signature. The method additionally can include providing thetransaction code to a mobile device being used by the consumer, suchthat the mobile device verifies the digital signature and sends arequest to pay the merchant for the payment amount from a first accountof the consumer maintained by a first financial institution, such thatthe first financial institution, upon receiving the request to pay,retrieves from a transaction system an account identifier of a secondaccount of the merchant maintained by a second financial institutionbased on the merchant public identifier, and such that the firstfinancial institution sends to the transaction system paymentinformation regarding a payment to be made to the second account fromthe first account. The transaction system can be maintained by an entitythat is different from the merchant, the first financial institution,and the second financial institution. The payment information can berouted through the transaction system to the second financialinstitution. The payment information can include the transactionidentifier, the account identifier of the second account, and thepayment amount. The method further can include receiving, at thepoint-of-sale terminal, a notification of payment for the transaction inreal-time while the consumer remains at the store of the merchant.

Additional embodiments include a system including one or more processorsand one or more non-transitory computer-readable media storing computinginstructions configured to run on the one more processors and performvarious acts. The acts can include receiving, at a mobile device beingused by a consumer, a transaction code from a point-of-sale terminal ata store of a merchant. The transaction code can include a merchantpublic identifier being associated with the merchant, a payment amountfor one or more items to be purchased from the merchant by the consumerin a transaction, a transaction identifier for the transaction, and adigital signature. The acts also can include verifying the digitalsignature for the transaction code. The acts additionally can includesending, from the mobile device, a request to pay the merchant for thepayment amount from a first account of the consumer maintained by afirst financial institution, such that the first financial institution,upon receiving the request to pay, retrieves from a transaction systeman account identifier of a second account of the merchant maintained bya second financial institution based on the merchant public identifier,such that the first financial institution sends to the transactionsystem payment information regarding a payment to be made to the secondaccount from the first account, such that the payment information isrouted through the transaction system to the second financialinstitution, and such that the point-of-sale terminal receives anotification of payment for the transaction in real-time while theconsumer remains at the store of the merchant. The transaction systemcan be maintained by an entity that is different from the merchant, thefirst financial institution, and the second financial institution. Thepayment information can include the transaction identifier, the accountidentifier of the second account, and the payment amount.

Further embodiments include a method being implemented via execution ofcomputing instructions configured to run at one or more processors andstored at one or more non-transitory computer-readable media. The methodcan include receiving, at a mobile device being used by a consumer, atransaction code from a point-of-sale terminal at a store of a merchant.The transaction code can include a merchant public identifier beingassociated with the merchant, a payment amount for one or more items tobe purchased from the merchant by the consumer in a transaction, atransaction identifier for the transaction, and a digital signature. Themethod also can include verifying the digital signature for thetransaction code. The method additionally can include sending, from themobile device, a request to pay the merchant for the payment amount froma first account of the consumer maintained by a first financialinstitution, such that the first financial institution, upon receivingthe request to pay, retrieves from a transaction system an accountidentifier of a second account of the merchant maintained by a secondfinancial institution based on the merchant public identifier, such thatthe first financial institution sends to the transaction system paymentinformation regarding a payment to be made to the second account fromthe first account, such that the payment information is routed throughthe transaction system to the second financial institution, and suchthat the point-of-sale terminal receives a notification of payment forthe transaction in real-time while the consumer remains at the store ofthe merchant. The transaction system can be maintained by an entity thatis different from the merchant, the first financial institution, and thesecond financial institution. The payment information can include thetransaction identifier, the account identifier of the second account,and the payment amount.

Additional embodiments include a system including one or more processorsand one or more non-transitory computer-readable media storing computinginstructions configured to run on the one more processors and performvarious acts. The acts can include receiving, at a first financialinstitution from a mobile device being used by a consumer, a request topay a merchant for a payment amount from a first account of the consumermaintained by the first financial institution. The request to pay caninclude information including a merchant public identifier, a paymentamount for one or more items to be purchased from the merchant by theconsumer in a transaction, and a transaction identifier for thetransaction. The mobile device can be used by the consumer at a store ofthe merchant to pay for the transaction. The information can be receivedby the mobile device from a point-of-sale terminal at the store of themerchant as part of a transaction code. The transaction code can beverified by the mobile device using a digital signature of thetransaction code. The acts also can include retrieving, at the firstfinancial institution from a transaction system, an account identifierfor a second account of the merchant maintained by a second financialinstitution based on the merchant public identifier. The transactionsystem can be maintained by an entity that is different from themerchant, the first financial institution, and the second financialinstitution. The acts additionally can include sending, from the firstfinancial institution to the transaction system, payment informationregarding a payment to be made to the second account from the firstaccount. The payment information can be routed through the transactionsystem to the second financial institution. The point-of-sale terminalcan receive a notification of payment for the transaction in real-timewhile the consumer remains at the store of the merchant. The paymentinformation can include the transaction identifier, the accountidentifier of the second account, and the payment amount.

Further embodiments include a method being implemented via execution ofcomputing instructions configured to run at one or more processors andstored at one or more non-transitory computer-readable media. The methodcan include receiving, at a first financial institution from a mobiledevice being used by a consumer, a request to pay a merchant for apayment amount from a first account of the consumer maintained by thefirst financial institution. The request to pay can include informationincluding a merchant public identifier, a payment amount for one or moreitems to be purchased from the merchant by the consumer in atransaction, and a transaction identifier for the transaction. Themobile device can be used by the consumer at a store of the merchant topay for the transaction. The information can be received by the mobiledevice from a point-of-sale terminal at the store of the merchant aspart of a transaction code. The transaction code can be verified by themobile device using a digital signature of the transaction code. Themethod also can include retrieving, at the first financial institutionfrom a transaction system, an account identifier for a second account ofthe merchant maintained by a second financial institution based on themerchant public identifier. The transaction system can be maintained byan entity that is different from the merchant, the first financialinstitution, and the second financial institution. The methodadditionally can include sending, from the first financial institutionto the transaction system, payment information regarding a payment to bemade to the second account from the first account. The paymentinformation can be routed through the transaction system to the secondfinancial institution. The point-of-sale terminal can receive anotification of payment for the transaction in real-time while theconsumer remains at the store of the merchant. The payment informationcan include the transaction identifier, the account identifier of thesecond account, and the payment amount.

Additional embodiments include a system including one or more processorsand one or more non-transitory computer-readable media storing computinginstructions configured to run on the one more processors and performvarious acts. The acts can include receiving, at a transaction systemfrom a first entity, a request including a merchant public identifierassociated with a merchant. The transaction system can be in datacommunication with a first financial institution that maintains a firstaccount of a consumer and a second financial institution that maintainsa second account of the merchant. The transaction system can bemaintained by an entity that is different from the merchant, the firstfinancial institution, and the second financial institution. Theconsumer can use a mobile device at a store of the merchant to pay forone or more items in a transaction. The mobile device can receive atransaction code from a point-of-sale terminal at the store. Thetransaction code can include a transaction identifier, a payment amountfor the transaction, the merchant public identifier, and a digitalsignature. The transaction code can be verified by the mobile deviceusing the digital signature of the transaction code. The acts also caninclude determining, at the transaction system, an account identifier ofthe second account based on the merchant public identifier using amerchant account database. The acts additionally can include sending theaccount identifier to the first financial institution. The acts furthercan include receiving, at the transaction system from the firstfinancial institution, payment information regarding a payment to bemade to the second account from the first account. The paymentinformation can include the account identifier of the second account,the payment amount, and the transaction identifier. The actsadditionally can include sending, from the transaction system to thesecond financial institution, the payment information, such that thepoint-of-sale terminal receives a notification of payment for thetransaction in real-time while the consumer remains at the store of themerchant.

Further embodiments include a method being implemented via execution ofcomputing instructions configured to run at one or more processors andstored at one or more non-transitory computer-readable media. The methodcan include receiving, at a transaction system from a first entity, arequest including a merchant public identifier associated with amerchant. The transaction system can be in data communication with afirst financial institution that maintains a first account of a consumerand a second financial institution that maintains a second account ofthe merchant. The transaction system can be maintained by an entity thatis different from the merchant, the first financial institution, and thesecond financial institution. The consumer can use a mobile device at astore of the merchant to pay for one or more items in a transaction. Themobile device can receive a transaction code from a point-of-saleterminal at the store. The transaction code can include a transactionidentifier, a payment amount for the transaction, the merchant publicidentifier, and a digital signature. The transaction code can beverified by the mobile device using the digital signature of thetransaction code. The method also can include determining, at thetransaction system, an account identifier of the second account based onthe merchant public identifier using a merchant account database. Themethod additionally can include sending the account identifier to thefirst financial institution. The method further can include receiving,at the transaction system from the first financial institution, paymentinformation regarding a payment to be made to the second account fromthe first account. The payment information can include the accountidentifier of the second account, the payment amount, and thetransaction identifier. The method additionally can include sending,from the transaction system to the second financial institution, thepayment information, such that the point-of-sale terminal receives anotification of payment for the transaction in real-time while theconsumer remains at the store of the merchant.

Additional embodiments include a system including one or more processorsand one or more non-transitory computer-readable media storing computinginstructions configured to run on the one more processors and performvarious acts. The acts can include performing, at a mobile device beingused by a consumer, an identity authentication of the consumer. The actsalso can include receiving, at the mobile device, first information froma point-of-sale terminal at a store of a merchant. The first informationcan include a merchant identifier, a transaction identifier, and apayment amount. The merchant identifier can be associated with themerchant. The payment amount can be for one or more items to bepurchased from the merchant by the consumer in a transaction. Thetransaction identifier can be associated with the transaction. The actsadditionally can include sending, from the mobile device, a request topay the merchant for the payment amount from one or more first accountsof the consumer maintained by a first financial institution, such thatthe first financial institution, upon receiving the request to pay,retrieves from a transaction system an account identifier of a secondaccount of the merchant maintained by a second financial institutionbased on the merchant identifier, such that the first financialinstitution sends to the transaction system payment informationregarding a payment to be made to the second account from the one ormore first accounts, such that the payment information is routed throughthe transaction system to the second financial institution, and suchthat the point-of-sale terminal receives a notification of payment forthe transaction in real-time while the consumer remains at the store ofthe merchant. The one or more first accounts can include at least onenon-demand deposit account. The transaction system can be maintained byan entity that is different from the merchant, the first financialinstitution, and the second financial institution. The paymentinformation can include the transaction identifier, the accountidentifier of the second account, and the payment amount.

Further embodiments include a method being implemented via execution ofcomputing instructions configured to run at one or more processors andstored at one or more non-transitory computer-readable media. The methodcan include performing, at a mobile device being used by a consumer, anidentity authentication of the consumer. The method also can includereceiving, at the mobile device, first information from a point-of-saleterminal at a store of a merchant. The first information can include amerchant identifier, a transaction identifier, and a payment amount. Themerchant identifier can be associated with the merchant. The paymentamount can be for one or more items to be purchased from the merchant bythe consumer in a transaction. The transaction identifier can beassociated with the transaction. The method additionally can includesending, from the mobile device, a request to pay the merchant for thepayment amount from one or more first accounts of the consumermaintained by a first financial institution, such that the firstfinancial institution, upon receiving the request to pay, retrieves froma transaction system an account identifier of a second account of themerchant maintained by a second financial institution based on themerchant identifier, such that the first financial institution sends tothe transaction system payment information regarding a payment to bemade to the second account from the one or more first accounts, suchthat the payment information is routed through the transaction system tothe second financial institution, and such that the point-of-saleterminal receives a notification of payment for the transaction inreal-time while the consumer remains at the store of the merchant. Theone or more first accounts can include at least one non-demand depositaccount. The transaction system can be maintained by an entity that isdifferent from the merchant, the first financial institution, and thesecond financial institution. The payment information can include thetransaction identifier, the account identifier of the second account,and the payment amount.

Additional embodiments include a system including one or more processorsand one or more non-transitory computer-readable media storing computinginstructions configured to run on the one more processors and performvarious acts. The acts can include receiving, at a first financialinstitution from a mobile device being used by a consumer, a request topay a merchant for a payment amount from one or more first accounts ofthe consumer maintained by the first financial institution. The one ormore first accounts can include at least one non-demand deposit account.The request to pay can include information including a merchantidentifier, a payment amount for one or more items to be purchased fromthe merchant by the consumer in a transaction, and a transactionidentifier for the transaction. The mobile device can be used by theconsumer at a store of the merchant to pay for the transaction. Theinformation can be received by the mobile device from a point-of-saleterminal at the store of the merchant. The acts also can includeretrieving, at the first financial institution from a transactionsystem, an account identifier for a second account of the merchantmaintained by a second financial institution based on the merchantidentifier. The transaction system can be maintained by an entity thatis different from the merchant, the first financial institution, and thesecond financial institution. The acts additionally can include sending,from the first financial institution to the transaction system, paymentinformation regarding a payment to be made to the second account fromthe one or more first accounts, such that the payment information isrouted through the transaction system to the second financialinstitution, and such that the point-of-sale terminal receives anotification of payment for the transaction in real-time while theconsumer remains at the store of the merchant. The payment informationcan include the transaction identifier, the account identifier of thesecond account, and the payment amount.

Further embodiments include a method being implemented via execution ofcomputing instructions configured to run at one or more processors andstored at one or more non-transitory computer-readable media. The methodcan include receiving, at a first financial institution from a mobiledevice being used by a consumer, a request to pay a merchant for apayment amount from one or more first accounts of the consumermaintained by the first financial institution. The one or more firstaccounts can include at least one non-demand deposit account. Therequest to pay can include information including a merchant identifier,a payment amount for one or more items to be purchased from the merchantby the consumer in a transaction, and a transaction identifier for thetransaction. The mobile device can be used by the consumer at a store ofthe merchant to pay for the transaction. The information can be receivedby the mobile device from a point-of-sale terminal at the store of themerchant. The method also can include retrieving, at the first financialinstitution from a transaction system, an account identifier for asecond account of the merchant maintained by a second financialinstitution based on the merchant identifier. The transaction system canbe maintained by an entity that is different from the merchant, thefirst financial institution, and the second financial institution. Themethod additionally can include sending, from the first financialinstitution to the transaction system, payment information regarding apayment to be made to the second account from the one or more firstaccounts, such that the payment information is routed through thetransaction system to the second financial institution, and such thatthe point-of-sale terminal receives a notification of payment for thetransaction in real-time while the consumer remains at the store of themerchant. The payment information can include the transactionidentifier, the account identifier of the second account, and thepayment amount.

Additional embodiments include a system including one or more processorsand one or more non-transitory computer-readable media storing computinginstructions configured to run on the one more processors and performvarious acts. The acts can include receiving, at a transaction systemfrom a first entity, a request including a merchant identifierassociated with a merchant. The transaction system can be in datacommunication with a first financial institution that maintains one ormore first accounts of a consumer and a second financial institutionthat maintains a second account of the merchant. The one or more firstaccounts can include at least one non-demand deposit account. Thetransaction system can be maintained by an entity that is different fromthe merchant, the first financial institution, and the second financialinstitution. The consumer can use a mobile device at a store of themerchant to authorize paying a payment amount for one or more items in atransaction using the one or more first accounts. The acts also caninclude determining, at the transaction system, an account identifier ofthe second account of the merchant maintained by a second financialinstitution using a merchant account database. The acts additionally caninclude sending the account identifier from the transaction system tothe first financial institution. The acts further can include receiving,at the transaction system from the first financial institution, paymentinformation regarding a payment to be made to the second account fromthe one or more first accounts. The payment information can include atransaction identifier, the account identifier of the second account,and the payment amount. The acts additionally can include sending, fromthe transaction system to the second financial institution, the paymentinformation, such that a point-of-sale terminal at the store of themerchant receives a notification of payment for the transaction inreal-time while the consumer remains at the store of the merchant.

Further embodiments include a method being implemented via execution ofcomputing instructions configured to run at one or more processors andstored at one or more non-transitory computer-readable media. The methodcan include receiving, at a transaction system from a first entity, arequest including a merchant identifier associated with a merchant. Thetransaction system can be in data communication with a first financialinstitution that maintains one or more first accounts of a consumer anda second financial institution that maintains a second account of themerchant. The one or more first accounts can include at least onenon-demand deposit account. The transaction system can be maintained byan entity that is different from the merchant, the first financialinstitution, and the second financial institution. The consumer can usea mobile device at a store of the merchant to authorize paying a paymentamount for one or more items in a transaction using the one or morefirst accounts. The method also can include determining, at thetransaction system, an account identifier of the second account of themerchant maintained by a second financial institution using a merchantaccount database. The method additionally can include sending theaccount identifier from the transaction system to the first financialinstitution. The method further can include receiving, at thetransaction system from the first financial institution, paymentinformation regarding a payment to be made to the second account fromthe one or more first accounts. The payment information can include atransaction identifier, the account identifier of the second account,and the payment amount. The method additionally can include sending,from the transaction system to the second financial institution, thepayment information, such that a point-of-sale terminal at the store ofthe merchant receives a notification of payment for the transaction inreal-time while the consumer remains at the store of the merchant.

Additional embodiments include a system including one or more processorsand one or more non-transitory computer-readable media storing computinginstructions configured to run on the one more processors and performvarious acts. The acts can include determining, at a point-of-saleterminal at a store of a merchant, a payment amount for one or moreitems to be purchased from the merchant by a consumer in a transaction.The acts also can include sending first information from thepoint-of-sale terminal to a mobile device used by the consumer. Thefirst information can include a merchant identifier, a transactionidentifier, and the payment amount, such that the mobile device sends arequest to pay the merchant for the payment amount from one or morefirst accounts of the consumer maintained by a first financialinstitution, such that the first financial institution, upon receivingthe request to pay, retrieves from a transaction system an accountidentifier of a second account of the merchant maintained by a secondfinancial institution based on the merchant identifier, such that thefirst financial institution sends to the transaction system paymentinformation regarding a payment to be made to the second account fromthe one or more first accounts, and such that the payment information isrouted through the transaction system to the second financialinstitution. The one or more first accounts can include at least onenon-demand deposit account. The transaction system can be maintained byan entity that is different from the merchant, the first financialinstitution, and the second financial institution. The paymentinformation can include the transaction identifier, the accountidentifier of the second account, and the payment amount. The actsadditionally can include receiving, at the point-of-sale terminal, anotification of payment for the transaction in real-time while theconsumer remains at the store of the merchant.

Further embodiments include a method being implemented via execution ofcomputing instructions configured to run at one or more processors andstored at one or more non-transitory computer-readable media. The methodcan include determining, at a point-of-sale terminal at a store of amerchant, a payment amount for one or more items to be purchased fromthe merchant by a consumer in a transaction. The method also can includesending first information from the point-of-sale terminal to a mobiledevice used by the consumer. The first information can include amerchant identifier, a transaction identifier, and the payment amount,such that the mobile device sends a request to pay the merchant for thepayment amount from one or more first accounts of the consumermaintained by a first financial institution, such that the firstfinancial institution, upon receiving the request to pay, retrieves froma transaction system an account identifier of a second account of themerchant maintained by a second financial institution based on themerchant identifier, such that the first financial institution sends tothe transaction system payment information regarding a payment to bemade to the second account from the one or more first accounts, and suchthat the payment information is routed through the transaction system tothe second financial institution. The one or more first accounts caninclude at least one non-demand deposit account. The transaction systemcan be maintained by an entity that is different from the merchant, thefirst financial institution, and the second financial institution. Thepayment information can include the transaction identifier, the accountidentifier of the second account, and the payment amount. The methodadditionally can include receiving, at the point-of-sale terminal, anotification of payment for the transaction in real-time while theconsumer remains at the store of the merchant.

Additional embodiments include a system including one or more processorsand one or more non-transitory computer-readable media storing computinginstructions configured to run on the one more processors and performvarious acts. The acts can include receiving a preauthorization code ata mobile device while the mobile device is in data communication with amobile wallet provider. The preauthorization code can include apreauthorization amount, an expiration time, and a digital signature.The acts also can include storing the preauthorization code in themobile device. The acts additionally can include receiving, at themobile device, an authorization from a user of the mobile device for atransaction having a transaction amount while the user is at apoint-of-sale terminal of a first entity. The acts further can includedetermining that the mobile device is unable to communicate with themobile wallet provider. The acts additionally can include verifying thatthe transaction amount is less than or equal to the preauthorizationamount. The acts further can include, while the mobile device is unableto communicate with the mobile wallet provider, providing a transactioncode from the mobile device to the point-of-sale terminal to cause thefirst entity to send the transaction amount and the preauthorizationcode to a transaction system, and to cause the transaction system tosend an approval for the transaction in real-time while the user remainsat the point-of-sale terminal of the first entity. The transaction codecan include the preauthorization code, a transaction identifier, and thetransaction amount.

Further embodiments include a method being implemented via execution ofcomputing instructions configured to run at one or more processors andstored at one or more non-transitory computer-readable media. The methodcan include receiving a preauthorization code at a mobile device whilethe mobile device is in data communication with a mobile walletprovider. The preauthorization code can include a preauthorizationamount, an expiration time, and a digital signature. The method also caninclude storing the preauthorization code in the mobile device. Themethod additionally can include receiving, at the mobile device, anauthorization from a user of the mobile device for a transaction havinga transaction amount while the user is at a point-of-sale terminal of afirst entity. The method further can include determining that the mobiledevice is unable to communicate with the mobile wallet provider. Themethod additionally can include verifying that the transaction amount isless than or equal to the preauthorization amount. The method furthercan include, while the mobile device is unable to communicate with themobile wallet provider, providing a transaction code from the mobiledevice to the point-of-sale terminal to cause the first entity to sendthe transaction amount and the preauthorization code to a transactionsystem, and to cause the transaction system to send an approval for thetransaction in real-time while the user remains at the point-of-saleterminal of the first entity. The transaction code can include thepreauthorization code, a transaction identifier, and the transactionamount.

Additional embodiments include a system including one or more processorsand one or more non-transitory computer-readable media storing computinginstructions configured to run on the one more processors and performvarious acts. The acts can include receiving a transaction amount and apreauthorization code from a first entity. The preauthorization code caninclude a preauthorization amount, an expiration time, and a digitalsignature. The transaction amount is for a transaction authorized by auser of a mobile device at a point-of-sale terminal of the first entity.The transaction amount is less than or equal to the preauthorizationamount. The mobile device received the preauthorization code and storedthe preauthorization code in the mobile device while the mobile devicewas in data communication with a mobile wallet provider. The mobiledevice provided a transaction code to the point-of-sale terminal whilethe mobile device was unable to communicate with the mobile walletprovider. The transaction code includes the preauthorization code, atransaction identifier for the transaction, and the transaction amount.The acts also can include verifying the preauthorization code using thedigital signature of the preauthorization code. The acts additionallycan include sending an approval for the transaction to the first entityin real-time while the user remains at the point-of-sale terminal of thefirst entity.

Further embodiments include a method being implemented via execution ofcomputing instructions configured to run at one or more processors andstored at one or more non-transitory computer-readable media. The methodcan include receiving a transaction amount and a preauthorization codefrom a first entity. The preauthorization code can include apreauthorization amount, an expiration time, and a digital signature.The transaction amount is for a transaction authorized by a user of amobile device at a point-of-sale terminal of the first entity. Thetransaction amount is less than or equal to the preauthorization amount.The mobile device received the preauthorization code and stored thepreauthorization code in the mobile device while the mobile device wasin data communication with a mobile wallet provider. The mobile deviceprovided a transaction code to the point-of-sale terminal while themobile device was unable to communicate with the mobile wallet provider.The transaction code includes the preauthorization code, a transactionidentifier for the transaction, and the transaction amount. The methodalso can include verifying the preauthorization code using the digitalsignature of the preauthorization code. The method additionally caninclude sending an approval for the transaction to the first entity inreal-time while the user remains at the point-of-sale terminal of thefirst entity.

Additional embodiments include a system including one or more processorsand one or more non-transitory computer-readable media storing computinginstructions configured to run on the one more processors and performvarious acts. The acts can include receiving a transaction code from amobile device at a point-of-sale terminal of a first entity while themobile device is unable to communicate with a mobile wallet provider.The transaction code can include a preauthorization code, a transactionidentifier for a transaction authorized by a user of the mobile deviceat the point-of-sale terminal, and a transaction amount for thetransaction. The mobile device received the preauthorization code andstored the preauthorization code in the mobile device while the mobiledevice was in data communication with the mobile wallet provider. Thepreauthorization code includes a preauthorization amount, an expirationtime, and a digital signature. The transaction amount is less than orequal to the preauthorization amount. The acts also can include sendingthe transaction amount and the preauthorization code to a transactionsystem. The acts additionally can include receiving an approval for thetransaction from the transaction system in real-time while the userremains at the point-of-sale terminal.

Further embodiments include a method being implemented via execution ofcomputing instructions configured to run at one or more processors andstored at one or more non-transitory computer-readable media. The methodcan include receiving a transaction code from a mobile device at apoint-of-sale terminal of a first entity while the mobile device isunable to communicate with a mobile wallet provider. The transactioncode can include a preauthorization code, a transaction identifier for atransaction authorized by a user of the mobile device at thepoint-of-sale terminal, and a transaction amount for the transaction.The mobile device received the preauthorization code and stored thepreauthorization code in the mobile device while the mobile device wasin data communication with the mobile wallet provider. Thepreauthorization code includes a preauthorization amount, an expirationtime, and a digital signature. The transaction amount is less than orequal to the preauthorization amount. The method also can includesending the transaction amount and the preauthorization code to atransaction system. The method additionally can include receiving anapproval for the transaction from the transaction system in real-timewhile the user remains at the point-of-sale terminal.

Additional embodiments include a system including one or more processorsand one or more non-transitory computer-readable media storing computinginstructions configured to run on the one more processors and performvarious acts. The acts can include receiving, at a mobile device from apoint-of-sale terminal of a first entity, an identifier of the firstentity, a transaction amount for a transaction, and a transactionidentifier for the transaction. The acts also can include receiving anauthorization from a user of the mobile device for the transaction whilethe user is at the point-of-sale terminal, the mobile device running amobile application that is associated with a mobile wallet provider. Theacts additionally can include determining that the mobile device isunable to communicate with the mobile wallet provider. The acts furthercan include generating an encrypted transaction code. The encryptedtransaction code can include a preauthorization from the user to pay thefirst entity for the transaction amount from a first account of the usermaintained by a first financial institution. The acts additionally caninclude sending the encrypted transaction code from the mobile device tothe point-of-sale terminal to cause the encrypted transaction code to besent through a proxy communication channel extending from thepoint-of-sale terminal, through a transaction system, to the mobilewallet provider, to cause the mobile wallet provider to decrypt theencrypted transaction code and verify the preauthorization from theuser, to cause the first financial institution to retrieve from thetransaction system an account identifier of a second account of thefirst entity maintained by a second financial institution based on theidentifier of the first entity and send to the transaction systempayment information regarding a payment to be made to the second accountfrom the first account for the transaction, to cause the paymentinformation to be routed through the transaction system to the secondfinancial institution, and to cause the point-of-sale terminal toreceive a notification of the payment for the transaction in real-timewhile the user remains at the point-of-sale terminal.

Further embodiments include a method being implemented via execution ofcomputing instructions configured to run at one or more processors andstored at one or more non-transitory computer-readable media. The methodcan include receiving, at a mobile device from a point-of-sale terminalof a first entity, an identifier of the first entity, a transactionamount for a transaction, and a transaction identifier for thetransaction. The method also can include receiving an authorization froma user of the mobile device for the transaction while the user is at thepoint-of-sale terminal, the mobile device running a mobile applicationthat is associated with a mobile wallet provider. The methodadditionally can include determining that the mobile device is unable tocommunicate with the mobile wallet provider. The method further caninclude generating an encrypted transaction code. The encryptedtransaction code can include a preauthorization from the user to pay thefirst entity for the transaction amount from a first account of the usermaintained by a first financial institution. The method additionally caninclude sending the encrypted transaction code from the mobile device tothe point-of-sale terminal to cause the encrypted transaction code to besent through a proxy communication channel extending from thepoint-of-sale terminal, through a transaction system, to the mobilewallet provider, to cause the mobile wallet provider to decrypt theencrypted transaction code and verify the preauthorization from theuser, to cause the first financial institution to retrieve from thetransaction system an account identifier of a second account of thefirst entity maintained by a second financial institution based on theidentifier of the first entity and send to the transaction systempayment information regarding a payment to be made to the second accountfrom the first account for the transaction, to cause the paymentinformation to be routed through the transaction system to the secondfinancial institution, and to cause the point-of-sale terminal toreceive a notification of the payment for the transaction in real-timewhile the user remains at the point-of-sale terminal.

Additional embodiments include a system including one or more processorsand one or more non-transitory computer-readable media storing computinginstructions configured to run on the one more processors and performvarious acts. The acts can include receiving, at a transaction systembeing situated along a proxy communication channel extending from apoint-of-sale terminal of a first entity to a mobile wallet provider, anencrypted transaction code. The encrypted transaction code can begenerated and sent to the point-of-sale terminal by a mobile device thatruns a mobile application associated with the mobile wallet provider.The mobile device receives from a point-of-sale terminal an identifierof the first entity, a transaction amount of a transaction, and atransaction identifier for the transaction, receives an authorizationfrom a user of the mobile device for the transaction while the user isat the point-of-sale terminal, and determines that the mobile device isunable to communicate with the mobile wallet provider. The encryptedtransaction code includes a preauthorization from the user to pay thefirst entity for the transaction amount from a first account of the usermaintained by a first financial institution. The acts also can includesending the encrypted transaction code through the proxy communicationchannel to the mobile wallet provider, to cause the mobile walletprovider to decrypt the encrypted transaction code and verify thepreauthorization from the user. The acts additionally can includereceiving, from the first financial institution, a request comprisingthe identifier of the first entity. The acts further can includedetermining an account identifier of a second account of the firstentity maintained by a second financial institution based on theidentifier of the first entity. The acts additionally can includesending the account identifier of the second account to the firstfinancial institution. The acts further can include receiving, from thefirst financial institution, payment information regarding a payment tobe made to the second account from the first account for thetransaction. The acts additionally can include sending the paymentinformation to the second financial institution, to cause thepoint-of-sale terminal to receive a notification in real-time while theuser remains at the point-of-sale terminal.

Further embodiments include a method being implemented via execution ofcomputing instructions configured to run at one or more processors andstored at one or more non-transitory computer-readable media. The methodcan include receiving, at a transaction system being situated along aproxy communication channel extending from a point-of-sale terminal of afirst entity to a mobile wallet provider, an encrypted transaction code.The encrypted transaction code can be generated and sent to thepoint-of-sale terminal by a mobile device that runs a mobile applicationassociated with the mobile wallet provider. The mobile device receivesfrom a point-of-sale terminal an identifier of the first entity, atransaction amount of a transaction, and a transaction identifier forthe transaction, receives an authorization from a user of the mobiledevice for the transaction while the user is at the point-of-saleterminal, and determines that the mobile device is unable to communicatewith the mobile wallet provider. The encrypted transaction code includesa preauthorization from the user to pay the first entity for thetransaction amount from a first account of the user maintained by afirst financial institution. The method also can include sending theencrypted transaction code through the proxy communication channel tothe mobile wallet provider, to cause the mobile wallet provider todecrypt the encrypted transaction code and verify the preauthorizationfrom the user. The method additionally can include receiving, from thefirst financial institution, a request comprising the identifier of thefirst entity. The method further can include determining an accountidentifier of a second account of the first entity maintained by asecond financial institution based on the identifier of the firstentity. The method additionally can include sending the accountidentifier of the second account to the first financial institution. Themethod further can include receiving, from the first financialinstitution, payment information regarding a payment to be made to thesecond account from the first account for the transaction. The methodadditionally can include sending the payment information to the secondfinancial institution, to cause the point-of-sale terminal to receive anotification in real-time while the user remains at the point-of-saleterminal.

Additional embodiments include a system including one or more processorsand one or more non-transitory computer-readable media storing computinginstructions configured to run on the one more processors and performvarious acts. The acts can include sending, to a mobile device from apoint-of-sale terminal of a first entity, an identifier of the firstentity, a transaction amount of a transaction, and a transactionidentifier for the transaction. The mobile device runs a mobileapplication that is associated with a mobile wallet provider, receivesan authorization from a user of the mobile device for the transactionwhile the user is at the point-of-sale terminal, determines that themobile device is unable to communicate with the mobile wallet provider,and generates an encrypted transaction code. The encrypted transactioncode includes a preauthorization from the user to pay the first entityfor the transaction amount from a first account of the user maintainedby a first financial institution. The acts also can include receivingthe encrypted transaction code from the mobile device. The actsadditionally can include sending the encrypted transaction code througha proxy communication channel extending from the point-of-sale terminal,through a transaction system, to the mobile wallet provider, to causethe mobile wallet provider to decrypt the encrypted transaction code andverify the preauthorization from the user, to cause the first financialinstitution to retrieve from the transaction system an accountidentifier of a second account of the first entity maintained by asecond financial institution based on the identifier of the first entityand send to the transaction system payment information regarding apayment to be made to the second account from the first account for thetransaction, and to cause the payment information to be routed throughthe transaction system to the second financial institution. The actsfurther can include receiving, at the point-of-sale terminal, anotification of the payment for the transaction in real-time while theuser remains at the point-of-sale terminal.

Further embodiments include a method being implemented via execution ofcomputing instructions configured to run at one or more processors andstored at one or more non-transitory computer-readable media. The methodcan include sending, to a mobile device from a point-of-sale terminal ofa first entity, an identifier of the first entity, a transaction amountof a transaction, and a transaction identifier for the transaction. Themobile device runs a mobile application that is associated with a mobilewallet provider, receives an authorization from a user of the mobiledevice for the transaction while the user is at the point-of-saleterminal, determines that the mobile device is unable to communicatewith the mobile wallet provider, and generates an encrypted transactioncode. The encrypted transaction code includes a preauthorization fromthe user to pay the first entity for the transaction amount from a firstaccount of the user maintained by a first financial institution. Themethod also can include receiving the encrypted transaction code fromthe mobile device. The method additionally can include sending theencrypted transaction code through a proxy communication channelextending from the point-of-sale terminal, through a transaction system,to the mobile wallet provider, to cause the mobile wallet provider todecrypt the encrypted transaction code and verify the preauthorizationfrom the user, to cause the first financial institution to retrieve fromthe transaction system an account identifier of a second account of thefirst entity maintained by a second financial institution based on theidentifier of the first entity and send to the transaction systempayment information regarding a payment to be made to the second accountfrom the first account for the transaction, and to cause the paymentinformation to be routed through the transaction system to the secondfinancial institution. The method further can include receiving, at thepoint-of-sale terminal, a notification of the payment for thetransaction in real-time while the user remains at the point-of-saleterminal.

Turning to the drawings, FIG. 1 illustrates a block diagram of a system100 that can be employed for a secure real-time payment transactionnetwork, according to an embodiment. System 100 is merely exemplary andembodiments of the system are not limited to the embodiments presentedherein. The system can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, certain elements, systems, or modules of system 100 canperform various procedures, processes, and/or activities. In otherembodiments, the procedures, processes, and/or activities can beperformed by other suitable elements, systems, or modules of system 100.

In some embodiments, system 100 can include one or more point-of-saleterminals, such as point-of-sale terminal 110; one or more mobiledevices, such as mobile device 120; two or more financial institutions,such as financial institutions 130 and 150; and/or a transaction system140. In other embodiments, system 100 also can include a wallet provider160. In a number of embodiments, each of the point-of-sale terminals,the one or more mobile devices, the two or more financial institution,and the transaction system can be or include a computer system, such ascomputer system 700, as shown in FIG. 7 and described below, and can bea single computer, a single server, or a cluster or collection ofcomputers or servers, or a cloud of computers or servers. In manyembodiments, various components (e.g., 110, 120, 130, 140, 150, 160) ofsystem 100 can be in data communication with various other components(e.g., 110, 120, 130, 140, 150, 160) of system 100, such as through oneor more networks. The networks can be the Internet and/or other suitablepublic and/or private data communication networks.

In various embodiments, point-of-sale terminal 110 can be located withina store of a merchant, such as merchant 119. In several embodiments, thestore can be a place of business, which can offer and/or sell items,such as products and/or services. In a number of embodiments,point-of-sale terminal 110 can be used to checkout a consumer 129 usingmobile device 120 for one or more items to be purchased by consumer 129.In many embodiments, point-of-sale terminal 110 can include one or moresystems, such as a checkout system 111, a communication system 112, apayment system 113, a consumer information system 114, a security system115, a preauthorization system 116, a proxy communication system 117,and/or other suitable systems. For example, in various embodiments,checkout system 111 can be used to determine the payment amount,communication system 112 can communicate with other components of system100, payment system 113 can determine whether consumer 129 hassatisfactorily paid for the one or more items to be purchased, consumerinformation system 114 can store information regarding consumer 129,security system 115 can be used to generate a merchant securitytransaction code, preauthorization system 116 can handle apreauthorization code from mobile device 120 when mobile device 120 isoffline, and/or proxy communication system 117 can handle proxycommunications through point-of-sale terminal 110 when mobile device 120is offline, as described below in further detail. In many embodiments,point-of-sale terminal 110 can be a register (e.g., cash register) thatincludes a card reader and communications with one or more card networks(e.g., STAR network, VISA network, etc.). In other embodiments,point-of-sale terminal 110 can be a register that is without a cardreader or the ability to communicate with card networks.

In a number of embodiments, mobile device 120 can be used by consumer129 to initiate a payment to merchant 119 for the one or more items tobe purchased. In various embodiments, mobile device 120 can run a mobileapplication 123, such as a mobile wallet, which can be employed tofacilitate paying merchant 119. In a number of embodiments, mobiledevice 120 and/or mobile application 123 can include one or moresystems, such as an authentication system 121, an account system 122, acommunication system 124, a security system 125, a loan system 126, astand-in credit system 127, a proxy communication system 128, and/orother suitable systems. For example, in various embodiments,authentication system 121 can verify the identity of consumer 129,account system 122 can provide information regarding a consumer accountof consumer 129, communication system 124 can communicate with othercomponents of system 100, security system 125 can decipher and/or decodethe merchant security transaction code and/or verify the digitalsignature of the merchant security transaction code, loan system 126 canpresent options and receive instructions regarding processing thetransaction at least partially using a loan or credit charge, stand-incredit system 127 can handle a preauthorization code to facilitatepayment when mobile device 120 is offline, and/or proxy communicationsystem 128 can handle proxy communications with point-of-sale terminal110 when mobile device 120 is offline, as described below in furtherdetail.

In several embodiments, when consumer 129 using mobile device 120 is atpoint-of-sale terminal 110 to checkout, point-of-sale terminal 110 candetermine the payment amount for the one or more items, and cancommunicate information to mobile device 120, such as the paymentamount, a merchant identifier, and/or a transaction identifier. In someembodiments, the merchant identifier can uniquely identify point-of-saleterminal 110. For example, in some embodiments, each point-of-saleterminal can have a unique merchant identifier. In a number ofembodiments, the merchant identifier can uniquely identify the merchant(e.g., merchant 119). For example, each merchant (e.g., merchant 119)can have a unique merchant identifier. In some embodiments, the merchantidentifier can be a token that can be associated with merchant 119and/or point-of-sale terminal 110. In many embodiments, when merchant119 sets up, configures, and/or reconfigures, point-of-sale terminal110, the merchant identifier can be created and/or assigned topoint-of-sale terminal 110. In the same or different embodiments, onepart of the merchant identifier can uniquely identify merchant 119, andanother part of the merchant identifier can uniquely identifypoint-of-sale terminal 110, such that the part of the merchantidentifier that uniquely identifies merchant 119 is the same for allpoint-of-sale terminals owned or used by merchant 119.

In various embodiments, mobile device 120 and point-of-sale terminal 110can communicate with each other (either one-way or two-way) using awireless data communication protocol. In some examples, thecommunication protocol can allow for one-way or two-way communication.For example, the wireless data communication protocol can be aproximity-based wireless data communication protocol, such as Near FieldCommunication (NFC), Bluetooth, Bluetooth Low Energy (BLE), iBeacon,etc. In other embodiments, mobile device 120 and/or point-of-saleterminal 110 can communicate with each other using another suitable formof communication. For example, in some embodiments, point-of-saleterminal 110 can provide a barcode (such as a QR (Quick Response) code),which can be scanned using a camera of mobile device 120, and/or mobiledevice 120 can provide a barcode (such as a QR code), which can bescanned using an optical scanner of point-of-sale terminal 110. In anumber of embodiments, communication system 112 can providecommunication functionality for point-of-sale terminal 110, and/orcommunication system 124 can provide communication functionality formobile device 120.

In several embodiments, transaction system 140 can be in datacommunication with various financial institutions, such as financialinstitution 130 and/or financial institution 150, and can provide forinteraction, facilitate communications, and/or facilitate transactionsbetween the financial institutions, such as financial institutions 130and 150. In a number of embodiments, transaction system 140 can includeone or more systems, such as a communication system 143, an accountsystem 144, a transaction system 145, a security system 146, apreauthorization system 147, a proxy communication system 148, and/orother suitable systems. In some embodiments, communication system 143can be used to provide communications with the financial institutions(e.g., 130, 150). In many embodiments, transaction system 140 caninclude a merchant account database 141 and/or a transaction database142, as described below in further detail. In some embodiments, accountsystem 144 can interface with merchant account database 141, and/ortransaction system 145 can interface with transaction database 142. In anumber of embodiments, security system 146 can interface with securitysystem 115 to facilitate providing a merchant security code, asdescribed below in further detail. In several embodiments,preauthorization system 147 can handle a preauthorization code frommobile device 120 when mobile device 120 is offline, and/or proxycommunication system 148 can handle proxy communications throughtransaction system 140 when mobile device 120 is offline, as describedbelow in further detail. In many embodiments, transaction system 140 caninclude a network system that facilitates communications between thevarious financial institutions (e.g., financial institution 130 andfinancial institution 150). This network system can have any suitabletopology, such as hub and spoke, peer-to-peer, or another suitabletopology.

In a number of embodiments, the financial institutions (e.g., 130, 150)can be depository financial institutions, such as savings banks, creditunions, savings and loan associations, card issuing financialinstitutions, or other forms of financial institutions. In a number ofembodiments, financial institution 130 can include one or more consumeraccounts 131 associated with consumer 129. In various embodiments,consumer accounts 131 can include one or more demand deposit accounts(e.g., a checking account, savings account, or cash balance account),and non-demand deposit accounts (i.e., an account other than a demanddeposit account), such as a lending account (e.g., a loan account or acredit account) or another type of account (e.g., a points account). Insome embodiments, financial institution 130 can include one or moresystems, such as a communication system 132, an authorization system133, an account system 134, a loan system 135, a preauthorization system136, a proxy communication system 137, and/or other suitable systems.For example, in some embodiments, account system 134 can interface withconsumer account 134 to provide information regarding the status of oneor more of consumer accounts 131, and/or can store and/or determineinformation regarding other accounts. In a number of embodiments,communication system 132 can communicate with other components of system100. In various embodiments, authorization system 133 can authorizepayments from one or more of consumer accounts 131. In a number ofembodiments, account system 134 can obtain information, such as balancesand statuses, about one or more of consumer accounts 131. In severalembodiments, preauthorization system 136 can handle generating apreauthorization code for mobile device 120 to facilitate transactionswhen mobile device 120 is offline, and/or proxy communication system 137can handle proxy communications through financial institution 130 whenmobile device 120 is offline, as described below in further detail.

In a number of embodiments, financial institution 150 can include amerchant account 151 associated with merchant 119. In variousembodiments, merchant account 151 can be a deposit account or anothersuitable type of account. In some embodiments, financial institution 150can include one or more systems, such as communication system 152,account system 153, a proxy communication system 154, and/or othersuitable systems, as described below in further detail. For example, insome embodiments, account system 153 can interface with merchant account151 to provide information regarding the status of merchant account 151,and/or can store and determine information regarding other accounts. Ina number of embodiments, communication system 152 can communicate withother components of system 100. In some embodiments, proxy communicationsystem 154 can handle proxy communications through financial institution150 when mobile device 120 is offline, as described below in furtherdetail.

In several embodiments, merchant account database 141 of transactionsystem 140 can store information regarding merchants (e.g., merchant119) and merchant accounts. For example, in a number of embodiments,merchant account database 141 can store a mapping between merchantidentifiers and merchant accounts. For example, a certain merchantidentifier can be associated with merchant 119 and merchant account 151of merchant 119 maintained by financial institution 150. When providedwith the merchant identifier, account system 144 and merchant accountdatabase 141 can be used by transaction system 140 to determine anaccount identifier (e.g., an account number) of merchant account 151,the name of merchant 119, a location of merchant 119, a location ofpoint-of-sale terminal 110, and/or other information regarding merchant119 and/or the merchant account. For example, in some embodiments,transaction system 140 can provide risk information (e.g., a risk score)regarding merchant 119 and/or merchant account 151. In some embodiments,a merchant can have three point-of-sale terminals, such as point-of-saleterminal 110, each with a unique identifier, which can each beassociated with a single account of merchant 119, specifically, merchantaccount 151.

In many embodiments, the merchant identifier can be a public identifierthat serves as an alias to identify merchant 119 and/or point-of-saleterminal 110 of merchant 119 among the various components (e.g., 110,120, 130, 140, 150, 160) of system 100. In a number of embodiments,merchant 119 can enroll and/or register with transaction system 140through financial institution 150, through a merchant consortium, ordirectly. In several embodiments, the merchant identifier for merchant119 and or point-of-sale terminal 110 of merchant 119 can be selectedand/or assigned at the time of enrollment or registration. In someembodiments, the merchant identifier can be a phone number, an emailaddress, a terminal identifier, or another suitable identifier. As partof enrollment and/or registration transaction system 140 can verify thatmerchant 119 is a legitimate (e.g., bona fide) merchant, such as byvetting merchant 119 through financial institution 150 and/or anotherenrollment entity.

In several embodiments, upon or after enrolling and/or registering withtransaction system 140, merchant 119 and/or point-of-sale terminal 110can be provided with a security system 115, which can be computinginstructions that are used to create a merchant security transactioncode. In some embodiments, security system 115 of point-of-sale terminal110 can communicate with security system 146 of transaction system 140,such as through application programming interface (API) calls. In otherembodiments, security system 115 of point-of-sale terminal 110 can beself-contained computing instructions (i.e., that do not call securitysystem 146 of transaction system 140) that are provided by transactionsystem 140 (e.g., at the time of enrollment and/or registration), or arebased on instructions and/or a software development kit (SDK) providedby transaction system 140 (e.g., at the time of enrollment and/orregistration).

In many embodiments, security system 115 can be used by merchant 119during a transaction to generate a merchant security transaction code.In many embodiments, the merchant security transaction code can includevarious information, such as the payment amount for the transaction, atransaction identifier that uniquely identifies the transaction tomerchant 119 and/or point-of-sale terminal 110, the merchant identifier,a date and/or time of the transaction, a list of the items purchased, adigital signature, and/or other suitable information. In manyembodiments, this information can be encoded in the merchant securitytransaction code using a suitable data encoding method. In manyembodiments, the digital signature can be generated based on the data inthe merchant security transaction code. The digital signature can begenerated using a suitable digital signature code signing algorithm aspart of a digital signature scheme. For example, the code signingalgorithm can be public-key cryptography signing algorithm, such asthose used in public key infrastructure (PKI), a cryptographic hashfunction, such as one of the Secure Hash Algorithm (SHA) published bythe National Institutes of Standards and Technology (NIST) (e.g.,SHA-256), or another suitable signing algorithm. The digital signaturecan be used to verify that merchant 119 created the merchant securitytransaction code and/or that the data in the merchant securitytransaction code has not been corrupted or tampered with after havingbeing created by security system 115.

In several embodiments, the merchant security transaction code can be adata code that can be transmitted between point-of-sale terminal 110 andmobile device 120 using a wireless data communication channel, asdescribed above. In other embodiments, the merchant security transactioncode can be encoded as a barcode, such as a one-dimensional (1D),two-dimensional (2D), or three-dimensional (3D) barcode, which can beoptically ready by mobile device 120, such as by using a camera onmobile device 120, as described above. For example, the merchantsecurity transaction code can be encoded as a matrix barcode, such as aQR code, and displayed on point-of-sale terminal 110 to be scanned by acamera on mobile device 120. In still other embodiments, the merchantsecurity transaction code can be transferred manually from point-of-saleterminal 110 to mobile device 120 by the merchant security transactioncode being displayed on point-of-sale terminal 110 and then beingmanually entered in mobile application 123 of mobile device 120.

In many embodiments, system 100 can provide a transaction network forsecure real-time payments. In several embodiments, mobile application123 of mobile device 120 can be used by consumer 129 to push a paymentfrom one or more of consumer accounts 131 to merchant account 151 tosatisfy an expectation of payment while consumer 129 is waiting atpoint-of-sale terminal 110. In a number of embodiments, mobileapplication 123 can be associated with and/or configured to beassociated with financial institution 130 and/or one or more of consumeraccounts 131. For example, account system 122 can associate mobileapplication 123 with one or more of consumer accounts 131 at financialinstitution 130. In some embodiments, mobile application 123 can beprovided by financial institution 130 as a mobile application for use onmobile device 120. In other embodiments, mobile application 123 can beassociated with multiple different financial institutions and accountsof consumer 129 at those financial institutions.

In some embodiments, mobile device 120 can be designed to be in datacommunication with mobile wallet provider 160. In many embodiments,mobile wallet provider 160 can communicate with mobile application 123on mobile device 120. In several embodiments, mobile wallet provider 160can be part of, or provided by, financial institution 130. For example,mobile application 123 can be an application provided by financialinstitution 130 for installation on mobile device 120. In otherembodiments, mobile wallet provider 160 can be part of, or provided by,transaction system 140. For example, mobile application 123 can be anapplication provided by the entity that operates transaction system 140for installation on mobile device 120. In still other embodiments,mobile wallet provider 160 can be part of, or provided by, anotherentity. For example, mobile wallet provider 160 can be another suitablemobile wallet provider, and can be similar or identical to Apple Pay byApple, Inc. of Cupertino, Calif., or Google Pay by Google, LLC ofMountain View, Calif., for example. In a number of embodiments, mobilewallet provider 160 can include a proxy communication system 161. Inseveral embodiments, proxy communication system 161 can handle proxycommunications through mobile wallet provider 160 when mobile device 120is offline, as described below in further detail.

In some embodiments, mobile wallet provider 160 can communicate withmobile device 120 through communication channel 171, mobile device 120can communicate with point-of-sale terminal 110 through communicationchannel 172, point-of-sale terminal 110 can communicate with financialinstitution 150 through communication channel 173, transaction system140 can communicate with financial institution 150 through acommunication channel 174, transaction system 140 can communicate withfinancial institution 130 through a communication channel 175, mobilewallet provider 160 can communicate with financial institution throughcommunication channel 176, transaction system 140 can communicate withmobile wallet provider through communication channel 177, and/ortransaction system 140 can communicate with point-of-sale terminal 110through communication channel 178. As described above, communicationchannel 171 can be a wireless data communication channel. In otherembodiments, communications between mobile device 120 and point-of-saleterminal 110 can be through done through optical scanning or manualmethods, as described above. In many embodiments, communication channels173, 174, 175, 176, 177, and/or 178 can be through the Internet or othersuitable networks. In some embodiments, transaction system 140 does notcommunicate with mobile wallet provider 160, such that communicationchannel 177 does not exist. In some embodiments, transaction system 140does not communicate with point-of-sale terminal, such thatcommunication channel 178 does not exist.

In many embodiments, communication channel 171 can be dependent onmobile device 120 being able to communicate with mobile wallet provider160. For example, mobile 120 can communicate with the Internet through acellular data network or through a wireless local area network. Ifeither of these communication channels is unavailable or not working, orif the Internet link to mobile wallet provider 160 is not working, andthus communication channel 171 is not working, mobile device 120 can becalled “offline,” or unable to communicate with mobile wallet provider160. When communication channel 171 is working, mobile device 120 can becalled “online,” or in data communication with mobile wallet provider160.

In several embodiments, financial institution 130 can generate apreauthorization code that includes a preauthorization amount and, insome embodiments, an expiration time. In many embodiments, thepreauthorization code can include a digital signature that indicatesthat financial institution 130 is the source of the preauthorizationcode. In many embodiments, preauthorization system 136 can generate thepreauthorization code. In a number of embodiments, the preauthorizationamount of the preauthorization code can be based on the account balanceof one or more consumer accounts 131. For example, the preauthorizationamount can be determined by preauthorization system 136 based on thecurrent balance and/or historical trends of the account balance. Inseveral embodiments, the expiration time can be a predetermined lengthof time, such as 30 minutes, 1 hour, 2 hours, 3 hours, 6 hours, 12hours, 24 hours, 2 days, 3 days, or 1 week, from the time that thepreauthorization code is generated. In other embodiments, the expirationtime can be determined based on the account balance, thepreauthorization amount, historical trends of the account balance,and/or other factors. In some embodiments, the digital signature can begenerated using a suitable digital signature code signing algorithm aspart of a digital signature scheme, similarly as described above for themerchant security transaction code. In many embodiments, thepreauthorization code can be sent through mobile wallet provider 160 tomobile device 120 and stored in mobile device 120 while mobile device120 is online. In several embodiments, the preauthorization code canprovide a “stand-in” credit in mobile device 120, which can allowconsumer 129 to conduct a transaction using mobile device 120 if mobiledevice 120 is offline at the time of the transaction. For example, thestand-in credit can allow consumer 129 to conduct a transaction thatdoes not exceed the preauthorization amount, provided that theexpiration time has not yet passed.

In many embodiments, the preauthorization code can be verified bypoint-of-sale terminal 110, merchant 119, financial institution 150,and/or transaction system 140. For example, the digital signature in thepreauthorization code can be verified to ensure that thepreauthorization code was authorized by financial institution 130 and/ormobile wallet provider 160. In some embodiments, this verification canbe done at merchant 119, such as in point-of-sale terminal 110, or canbe done in financial institution 150 and/or transaction system 140. Forexample, a public key of financial institution 130 can be used to verifythe digital signature.

In many embodiments, merchant account 151 at financial institution 150can receive payment from consumer account 131 at financial institution130, based on the verified preauthorization. In some embodiments, adebit pull can be done in real time or later (e.g., in nightly batchprocessing), but funds can be made available immediately to merchant 151based on the preauthorized promise from financial institution 130. Inother embodiments, the payment can be effectuated later after mobiledevice 120 comes back online and communicates with mobile walletprovider 160 to initiate the payment, or after a timeout period.

In several embodiments, mobile application 123 can provide informationto consumer 129 regarding the status of one or more of consumer accounts131 and availability of funds in one or more of consumer accounts 131,or the stand-in credit amount stored in mobile device 120. For example,account system 122 of mobile device 120 can obtain information fromaccount system 134 of financial institution 130 regarding one or more ofconsumer accounts 131 and provide that information to consumer 129. Forexample, if one of consumer accounts 131 has an available balance and/oravailable credit of $500, mobile application 123 can communicate theamount of the available funds for one or more of consumer accounts 131to consumer 129, which can allow consumer 129 to know the amount of theavailable funds for spending before shopping for items and/or beforeattempting to purchase items. In a number of embodiments, account system134 can provide account system 122 with various other information, suchas the current status of one or more of consumer accounts 131, such aswhether one or more of consumer accounts 131 is open and in good status(or closed), whether one or more of consumer accounts 131 has had recentnot sufficient funds (NSF) activity, whether one or more of consumeraccounts 131 has a stop payment order, and/or a buying power index ofconsumer 129 at least partially based on information about one or moreof consumer accounts 131.

In some embodiments, mobile application 123 can be used on mobile device120 at point-of-sale terminal 110 to conduct a transaction. In severalembodiments, mobile device 120 can receive the merchant identifier andother transaction information from point-of-sale terminal 110 ofmerchant 119. The merchant identifier can be associated with merchantaccount 151 of merchant 119. After receiving the merchant identifier,mobile application 123 can initiate a push payment from one or more ofconsumer accounts 131 at financial institution 130 to merchant account151 at financial institution 150 to complete the transaction inreal-time before the consumer leaves the store of merchant 119. In manyembodiments, mobile device 120 can receive the merchant identifier andother transaction information from point-of-sale terminal 110 as part ofthe merchant security transaction code.

In various embodiments, authentication system 121 can verify theidentity of consumer 129. For example, authentication system 121 canverify the identity of consumer 129 using a personal identificationnumber (PIN), a password, one or more fingerprints, voice recognition,other biometrics (e.g., mobile phone bio-measurements), and/or othersuitable authentication methods, to ensure that consumer 129 isauthorized to associate mobile application 123 with one or more ofconsumer accounts 131 and/or make payments using mobile application 123.

In a number of embodiments, when mobile application 123 is used toconduct a transaction, mobile device 120 can be put in the proximity ofpoint-of-sale terminal 110 to allow communication system 124 to receiveinformation from point-of-sale terminal 110, such as the payment amount,the merchant identifier, a transaction identifier, and/or otherinformation, such as the merchant name, the date and time, a list ofSKUs (stock keeping units) of the one or more items to be purchased,etc. In many embodiments, mobile device 120 can receive the merchantidentifier and other transaction information from point-of-sale terminal110 as part of the merchant security transaction code. In severalembodiments, security system 125 of mobile device 120 can verify thedigital signature in the merchant security transaction code. Forexample, security system 125 can verify the digital signature using asignature verifying algorithm that is part of the same digital signaturescheme that was used to digitally sign the merchant security transactioncode. For example, a public key for merchant 119 can be used to verifythe digital signature and the merchant security transaction code. Byverifying the digital signature of the merchant security transactioncode, security system 125 can verify that the merchant identifier isfrom point-of-sale terminal 110 of merchant 119 and is accurate, whichcan advantageously ensure that the funding from consumer accounts 131will be sent to an account actually associated with the merchant insteadof a fraudster.

In some embodiments, mobile application 123 can be configured to allowone-click checkout, which can be enabled by selecting a button on mobileapplication 123 or by placing mobile device 120 in the proximity of adata transmitter on point-of-sale terminal 110. In some embodiments,mobile application 123 can be configured to scan items and conducttransactions in real-time as items are taken from the shelf and scannedby mobile device 120 or placed within a “smart” shopping cart, such thatcheckout can take place in an aisle of the store, rather than atpoint-of-sale terminal 110. In other embodiments, checkout can takeplace automatically when consumer 129 exits the store of merchant 119.In a number of embodiments, mobile application 123 can receive themerchant identifier upon entering the store of merchant 119 or from ashopping cart having data transmitted in the store of merchant 119.

In some embodiments, the mobile application 123 can send informationfrom mobile device 120 to point-of-sale terminal 110, such asinformation regarding consumer 129, such as personally identifiableinformation, loyalty rewards number(s), shopping patterns, points,buying power index, and/or other suitable information. In severalembodiments, consumer information system 114 can process the informationprovided from mobile application 123 to provide information to merchant119 regarding consumer 129. In some embodiments, mobile device 120 cancommunicate information, such as a buying power index, to point-of-saleterminal 110 and/or merchant 119 upon entering the store of merchant119.

In several embodiments, consumer 129 can decide whether to authorize thetransaction using mobile device 120. For example, mobile device 120 canask consumer 129 to approve the transaction in mobile application 123.In a number of embodiments, mobile application 123 can present the oneor more of consumer accounts 131 to consumer 129 to select which of theconsumer accounts 131 to use to fund the transaction. In someembodiments, consumer 129 can choose to split the funding of thetransaction among multiple accounts. For example, consumer 129 canchoose to fund 20% of the transaction from a demand deposit account(e.g., a debit account) and 80% of the transaction from a non-demanddeposit account (e.g., by a charge to a credit account). In someembodiments, if an account of the one or more of consumer accounts 131has an account balance that is less than the amount of the transaction(or the portion of the transaction that consumer 129 has chosen toallocate to the account), loan system 126 of mobile device 120 candetermine that there is a deficiency and can present an option to fundthe transaction (or a portion of the transaction) using a non-demanddeposit account, such as a loan account, a credit account, or a pointsaccount. In other embodiments, loan system 126 can present the optionfor funding the transaction through a non-demand deposit account even ifthere is no deficiency in the one or more of consumer accounts 129.

In some embodiments, the loan account can be a new account that iscreated upon consumer 129 choosing to fund the transaction (or portionthereof) with the loan account. In other embodiments, the loan accountcan be for a previously authorized loan. In some embodiments, the loanaccount can have a pre-existing loan balance, which can be increasedbased on the amount of loan used to the fund the transaction. In severalembodiments, the loan can be a small loan, and can be labeled a“micro-loan”), but can be treated the same as credit line for a loaninstead of an overdraw of an account.

In several embodiments, consumer 129 can make the decision from whichaccount or accounts to fund the transaction, and/or to authorize a loanor a credit transaction, while at or near the point-of-sale terminal 110in the store of merchant 119. In the same or other embodiments, loansystem 126 can allow consumer 129 to choose the one or more accountsfrom which to fund the transaction after consumer 129 has left thestore. In many embodiments, financial institution 130 can fund thetransaction temporarily from a shadow account that the bank uses to fundoverdraft transaction, which can be reimbursed from the one or moreaccounts selected by consumer 129. For example, consumer 129 canauthorize a transaction at point-of-sale terminal 110 in the store, andfinancial institution 130 can authorize transfer of funds to financialinstitution 150 to pay merchant 119, and after consumer 129 leaves thestore of merchant 129, loan system 126 can push a message to consumer129 asking for one or more of consumer accounts 131 that consumer 129wants to use to fund the transaction. The options of consumer accounts131 can include the option to open a new loan account, or to add to thebalance of an existing loan account. In some embodiments, consumer 129can setup a list (e.g., prioritized list) of consumer accounts 131 touse for transaction using mobile device 120, and/or can setupbefore-hand an amount and/or percentage to use from one or more of theaccounts. For example, consumer 129 can choose to use a debit accountfor the first $50 and then use a credit account for the rest. As anotherexample, consumer 129 can choose to use a debit account for 40% of thetransaction, and use a new micro-loan for the rest.

In some embodiments, a points account can be used to pay for all or atleast a portion of the payment. For example, consumer 129 can have apoints account at financial institution 130, which can have a balance ofpoints earned by consumer 129 at financial institution 130. In manyembodiments, these points can have an exchange value, such that thepoints can be redeemed to pay for all or at least a portion of thepayment.

In a number of embodiments, if mobile device 120 is offline, thestand-in credit can be presented as an option to fund the transaction.In other embodiments, if mobile device 120 is offline, mobile device 120can communicate with point-of-sale terminal 110 to communicate through aproxy communication channel. In many embodiments, the proxycommunication channel can extend from point-of-sale terminal 110 tomobile wallet provider 160. For example, in some embodiments, the proxycommunication channel can comprise communication channels 173, 174, and177, and can extend through financial institution 150 and transactionsystem 140. In other embodiments, the proxy communication channel cancomprise communication channels 173, 174, 175, and 176, and can extendthrough financial institution 150, transaction system 140, and financialinstitution 130. In still other embodiments, the proxy communicationchannel can comprise communication channels 178 and 177, and can extendthrough transaction system 140. In yet other embodiments, the proxycommunication channel can comprise communication channels 178, 175, and176, and can extend through transaction system 140 and financialinstitution 130. In a number of embodiments, the proxy communicationchannel also can include communication channel 172, and can extendthrough point-of-sale terminal 110. When mobile device 120 is offline,communication channel 171 is unavailable, so mobile device 120 cancommunicate with mobile wallet provider 160 instead using the proxycommunication channel.

In many embodiments, proxy communication system 128 can facilitate proxycommunications being sent from or received by mobile device 120. In anumber of embodiments, proxy communication system 117 can facilitateproxy communications sent from, received by, or through point-of-saleterminal 110. In some embodiments, proxy communication system 154 canfacilitate proxy communications through financial institution 150. Inseveral embodiments, proxy communication system 148 can facilitate proxycommunications through transaction system 140. In a number ofembodiments, proxy communication system 137 can facilitate proxycommunications through financial institution 130. In severalembodiments, proxy communication system 161 can facilitate proxycommunications received by or sent from mobile wallet provider 160.

In several embodiments, communications through the proxy communicationchannel can be encrypted. For example, a one-way message from mobiledevice 120 to mobile wallet provider 160 through the proxy communicationchannel can be encrypted using a public key of mobile wallet provider160, such that only mobile wallet provider 160 can decrypt the messageusing the private key of the mobile wallet provider, using a public-keyencryption algorithm. In some embodiments, a message from mobile device120 to mobile wallet provider 160 can be digitally signed by mobiledevice 120, such that the mobile wallet provider can verify that themessage originated from consumer 129 using mobile device 120. In otherembodiments, two-way encrypted communications can be established usinganother suitable cryptographic protocol, such as performing acryptographic handshake to create a secure encrypted connection throughthe proxy communication channel using symmetric cryptography with aprivate key, similar to Transport Layer Security (TLS). When the proxycommunication channel is used to send a message from mobile device 120to mobile wallet provider 160, the message received by mobile walletprovider 160 through the proxy communication channel can be treated thesame by mobile wallet provider 160 as a message from mobile device 120received by mobile wallet provider 160 through communication channel171.

In many embodiments, after mobile device 120 has communicated withpoint-of-sale terminal 110 using communication system 124 to receive themerchant identifier and other transaction information, and consumer 129has authorized the transaction, mobile device 120 can communicate withfinancial institution 130 and/or transaction system 140, through mobilewallet provider 160 (which, in some embodiments, can be part offinancial institution 130 or transaction system 140), to request apayment be made to merchant account 151 of merchant 119 from one or moreof consumer accounts 131. When mobile device 120 is online, mobiledevice 120 can communicate with mobile wallet provider 160 throughcommunication channel 170. In some embodiments, when mobile device 120is offline, mobile device 120 can communicate with mobile walletprovider 160 through the proxy communication channel described above,and then the request can be sent from mobile wallet provider 160 tofinancial institution 130. In some such embodiments, mobile device 120can generate an encrypted transaction code to be sent through the proxycommunication channel to mobile wallet provider 160. In manyembodiments, the encrypted transaction code can include apreauthorization from consumer 129 to pay a transaction amount. In anumber of embodiments, the preauthorization can be digitally signed bymobile device 120, such that the preauthorization can be verified bymobile wallet provider 160. In other embodiments, the stand-in creditcan be used, as described above and below in further detail.

In a number of embodiments, when mobile device 120 communicates withfinancial institution 130 (such as through mobile wallet provider 160,which, in some embodiments, can be part of financial institution 130) torequest a payment be made, account system 134 of financial institution130 can determine account information about merchant account 151, suchas the account identifier of merchant account 151, at least partiallybased on the merchant identifier received from mobile device 120. Insome embodiments, financial institution 130 can communicate withtransaction system 140) to get the account information about merchantaccount 151, which can be stored in merchant account database 141. Insome embodiments, financial institution 130 can save the accountinformation about merchant account 151 so financial institution does notneed to query the account information from merchant account database 141in transaction system 140 for future transaction involving the samemerchant identifier. In other embodiments, financial institution 130 canquery for the account information from merchant account database 141 intransaction system 140 for each new transaction, or at occasional and/orregular intervals. In other embodiments, when mobile device 120communicates with transaction system 140 through mobile wallet provider160 to request a payment be made, transaction system 140 can provide theaccount information about merchant account 151 to first financialinstitution 130. In still other embodiments, mobile device 120 cancommunicate to mobile wallet provider 160 through the proxycommunication channel, as described above.

In many embodiments, having the account information about merchantaccount 151, financial institution 130 can initiate a payment tofinancial institution 150 from one or more of consumer accounts 131 tomerchant account 151. In several embodiments, before initiating payment,authorization system 133 can determine whether to authorize payment fromone or more of consumer accounts 131. For example, financial institution130 can determine whether the payment amount is within the availablefunds in one or more of consumer accounts 131, determine whether one ormore of consumer accounts 131 is currently open and in good status (orclosed), authenticate the identity of consumer 129 using mobile device120, and/or perform other actions. For example, in some embodiments,authentication system 121 can authenticate the identity of consumer 129,and that information can be communicated from mobile device 120 tofinancial institution 130. In some embodiments, mobile device 120 canprompt consumer 129 to authenticate before and/or after mobile device120 receives the merchant identifier and/or the transaction informationfrom point-of-sale terminal 110.

In some embodiments, authorization system 133 can request additionalauthentication from authentication system 121 (which can be directlythrough a network between financial institution 130 and mobile device120, or can be through mobile wallet provider 160 and/or throughtransaction system 140) after receiving the request for payment frommobile device 120 and/or after receiving the information about merchant119 and/or merchant account 151. In a number of embodiments,authorization system 133 of financial institution 130 can performdifferent and/or varying levels of authentication based on variousfactors. For example, authentication system 121 and/or authorizationsystem 133 can determine whether mobile device 120 used to send therequest for payment has been previously used by consumer 129 fortransaction with financial institution 130, whether biometrics of theconsumer match stored biometrics of consumer 129, whether the requestedtransaction and associated details (e.g., the identity of merchant 119,the location of merchant 119, the payment amount, the one or more itemsto be purchased (e.g., a list of SKUs), and/or other suitable factors)are consistent with spending patterns of consumer 129, whether consumer129 has reported mobile device 120 lost or stolen, whether consumer 129has reported that credit cards, debit cards, or other information aboutone or more of consumer accounts 131 have been lost or stolen, and/orother suitable factors. In various embodiments, financial institution130 can adjust the level of authentication used to verify the identityof consumer 129 based on one or more of these factors, and/or based onthe payment amount, the identity of merchant 119, the location ofmerchant 119, historical spending of consumer 129, and/or other relevantinformation.

In some embodiments, if one or more of consumer accounts 131 chosen byconsumer 129 for the transaction is short on funds or otherwise cannotbe fully used, loan system 135 can communicate with loan system 126 topresent other funding options to consumer 129, such as the option for amicro-loan to fund all or part of the transaction, as described above.

In many embodiments, after receiving authorization from authorizationsystem 133, financial institution 130 can initiate a payment tofinancial institution 150 to transfer funds from one or more of consumeraccounts 131 to merchant account 151. In a number of embodiments, thepayment can be effected by sending payment information regarding apayment to be made to merchant account 151 from one or more of consumeraccounts 131. In a number of embodiments, the payment informationtransferred from financial institution 130 to financial institution 150can effectuate an authenticated credit push, which can irrevocablysatisfy payment to the merchant and/or ensure that the merchant has goodfunds when consumer 129 leaves the store of merchant 119. For example,the payment can be a settlement credit push of funds for the paymentamount from one or more of consumer accounts 131 to merchant account151, which can be settled immediately. In various embodiments, thepayment information transferred from financial institution 130 tofinancial institution 150 can effectuate a push promise to pay, whichcan provide an irrevocable guarantee of payment from financialinstitution 130 to financial institution 150. In several embodiments,for example, the payment can be an ACH (Automated Clearing House) creditpush, which can provide an irrevocable funding guarantee.

In many embodiments, the payment and/or the guarantee of payment can besent in real-time from financial institution 130 to financialinstitution 150, which can happen for each such transaction. In someembodiments, the settlement of the transaction can happen later, such asin a nightly batch fashion, and in some embodiments, can happen througha different network, such as an ACH network or a credit network. Inother embodiments, the real-time payment and/or guarantee of payment canbe processed through an ACH network or a credit network. In someembodiments, the consumer can provide instructions to financialinstitution 130 to label the transaction as a debit or a credittransaction in one or more of consumer accounts 131, and in someembodiments can provide such instructions with the request to pay, orbefore or after the request to pay. In some embodiments, a credittransaction can be treated as a micro-loan, as described above. Incertain embodiments, a debit pull with guaranteed promise to pay can beused, such that financial institution 150 can receive a guaranteedpromise to pay from financial institution 130 and pull the funds using adebit pull.

In various embodiments, transaction system 140 can store informationregarding each transaction in transaction database 142. In severalembodiments, transaction system 140 can serve as a central auditor fortransactions between the financial institutions (e.g., 130, 150) in datacommunication with transaction system 140. In some embodiments,transaction system 140 can receive some or all of the information fromthe merchant security transaction code. In various embodiments, one ormore portions of the merchant security transaction code can be encryptedby security system 115. For example, the merchant security transactioncode can include an encrypted portion that can be decrypted by securitysystem 146 of transaction system 140, which can be used to ensure thatthe message has not been tampered. In other embodiments, the merchantsecurity transaction code is not encrypted, but is digitally signed, asdescribed above, and the digital signature can be verified, in someembodiments, by security system 146, which can advantageously ensurethat the merchant identifier correctly identifies merchant 119, so thatthe funds are paid to merchant account 151 corresponding to merchant119.

In a number of embodiments, financial institution 150, upon receivingpayment and/or guarantee of payment, can notify point-of-sale terminal110 and/or merchant 119 in real-time that merchant 119 hassatisfactorily received payment from consumer 129. For example, thenotification can include various information, such as the transactionidentifier, the amount received in payment (or guarantee), the merchantidentifier, and/or other information. Receiving the notice of good fundscan allow merchant 119 to proceed, such as, for example, to allowconsumer to leave the store of merchant 119 with the items. In someembodiments, for example, point-of-sale terminal 110 can match thenotification to the pending transaction in point-of-sale terminal 110using the transaction identifier. In certain embodiments, merchant 119can match the notification to the point-of-sale terminal using themerchant identifier. In some embodiments, consumer 129 can receive anotification on mobile device 120 that the transaction has cleared, suchas shown in FIG. 22 and described below.

In several embodiments, system 100 can advantageously provide a numberof technological improvements that can overcome technological problemsin conventional systems. For example, in several embodiments, system 100can beneficially allow consumer 129 to send payment directly and/orimmediately to merchant 119 when consumer 129 is checking out atpoint-of-sale terminal 110. In many embodiments, the payment systems andmethods provided by system 100 described herein can eliminate theacquirer model that is conventionally used in payment card transactions.In several embodiments, the payment systems and methods provided bysystem 100 described herein can advantageously streamline payments byeliminating the need for the financial institution (i.e., the acquirer)of merchant 119 to request payment from the financial institution (i.e.,the issuer) of consumer 129. For example, in many embodiments, financialinstitution 150 does not need to request payment from financialinstitution 130. In many embodiments, the payment systems and methodsprovided by system 100 described herein can beneficially ensuremerchants (e.g., merchant 119) are paid by consumers (e.g., consumer129) while eliminating and/or reducing many of the transaction fees paidto various entities in the conventional model.

In a number of embodiments, the payment systems and methods provided bysystem 100 described herein can advantageously eliminate the chargebackliability of merchants for fraudulent transactions. In the conventionalacquirer-issuer model, the merchant (e.g., 119) is responsible forverifying the credit or debit card to ensure that the card is not beingused fraudulently. In several embodiments, the payment systems andmethods provided by system 100 described herein can beneficially placethe liability on the financial institution (e.g., 130) of the consumer(e.g. 129), which can be in a better position (e.g., with more and/orbetter information) than the merchant (e.g., 119) to determine if therequest to pay is a legitimate, authentic transaction requested by theconsumer (e.g., 129) and/or if the consumer's account is still open andin good status (or closed), has sufficient funds, etc. In variousembodiments, the payment systems and methods provided by system 100described herein can advantageously allow the financial institution(e.g., 130) of the consumer (e.g., 129) to choose how to authenticatethe consumer (e.g., 129), and/or can beneficially allow the financialinstitution (e.g., 130) of the consumer (e.g., 129) to choose the levelof authentication, which can be tailored for each consumer (e.g., 129)and/or for each transaction (e.g., the financial institution (e.g., 130)can decide, at least partially based on its risk determination, that atransaction with a higher payment amount warrants a higher level ofauthentication). In several embodiments, the liability for fraudulentuse of one or more of the consumer accounts (e.g., 131) can be placed onthe consumer (e.g., 129), and/or the consumer (e.g., 129) can choose thelevel of authentication used by the financial institution (e.g., 130) ofthe consumer (e.g., 129). In many embodiments, unauthorized access toone or more of consumer accounts 131 can beneficially be reduced and/oreliminated using the payment method provided by system 100 and describedherein.

In several embodiments, the payment systems and methods provided bysystem 100 described herein can beneficially provide the ability forfinancial institution 130 to communicate directly with consumer 129 atpoint-of-sale terminal 110 when making a transaction. In manyembodiments, the payment systems and methods provided by system 100described herein can provide information to consumer 129, such asaccount balance, insufficient funds, lock/freeze on one or more ofconsumer accounts 131, etc., in real-time before consumer 129 requestspayments, which can advantageously eliminate and/or reduce negativeexperiences of consumer 129, such as attempting to transact withinsufficient funds or a freeze on one or more of consumer accounts 131.In a number of embodiments, the payment systems and methods provided bysystem 100 described herein can beneficially provide consumer 129 withthe ability the ability to split the payment with one or more otheraccounts or a new loan, such as a micro-loan, which can allow consumer129 to successfully make the payment and reduce negative experiences ofconsumer 129.

In some embodiments, account information about one or more of consumeraccounts 131 can beneficially be better protected from theft by thepayment systems and methods provided by system 100 described herein,because, in a number of embodiments, the account information of one ormore of consumer accounts 131 and/or personally identifiable informationof consumer 129 can be undisclosed to third parties other than financialinstitution 130, which maintains consumer accounts 131. For example, insome embodiments, the account information of consumer accounts 131and/or personally identifiable information of consumer 129 can beundisclosed to point-of-sale terminal 110, merchant 119, transactionsystem 140, and/or financial institution 150. In many embodiments, theaccount identifier (e.g., account number) of consumer accounts 131 isnot sent across any networks, but resides solely in financialinstitution 130, which can beneficially prevent that information frombeing stolen. For example, the many recent large-scale data breaches ofmerchant systems that have exposed consumer account information andpersonally identifiable information of millions of consumers could havebeen mitigated by using the payment systems and methods provided bysystem 100 and described herein.

In other embodiments, consumer 129 can choose to provide accountinformation of one or more of consumer accounts 131 and/or personallyidentifiable information of consumer 129 to one or more third parties.For example, in some embodiments consumer 129 can set privacyinstructions in mobile device 120 and/or with financial institution 130regarding what information can be disclosed to third parties. Forexample, consumer 129 can elect to disclose certain information tomerchant 119 in order to receive discounts, point, and/or other perksfrom merchant 119. For example, in some embodiments, financialinstitution 130 can send certain personally identifiable information ofconsumer 129 through transaction system 140 to financial institution 150along with the payment information, and financial institution 150 canprovide the information to merchant 119. In the same or otherembodiments, mobile device 120 can provide certain personallyidentifiable information of consumer 129 to merchant 119, such asthrough the wireless data communication protocol. Examples of suchpersonally identifiably information can include a name, a home address,a telephone number, a social security number, a tax identificationnumber, an age, an income level, marital status, a number of dependents,a frequent shopper identifier, shopping preferences, etc.

In various embodiments, the payment systems and methods provided bysystem 100 described herein also can beneficially shield the accountinformation about merchant account 151 from being disclosed outside anetwork of financial institutions (e.g., 130, 150) and transactionsystem 140, which can beneficially prevent theft and misuse of theaccount information about merchant account 151.

In a number of embodiments, the payment systems and methods provided bysystem 100 described herein can advantageously allow mobile device 120to make a payment to merchant 119 when mobile device 120 is offline orunable to communicate with mobile wallet provider 160. For example, asdescribed herein, mobile device 120 can store a stand-in credit that canbe used to initiate payment when mobile device 120 cannot communicatewith mobile wallet provider 160 and/or when financial institution 130 isunavailable for communication. As another example, as described herein,mobile device can communicate to point-of-sale terminal to communicatethrough a proxy communication channel to mobile wallet provider 160.

Turning ahead in the drawings, FIG. 2 illustrates a flow chart for amethod 200, according to an embodiment. In some embodiments, method 200can be a method of facilitating secure payment transactions. Method 200is merely exemplary and is not limited to the embodiments presentedherein. Method 200 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, the procedures, the processes, and/or the activities ofmethod 200 can be performed in the order presented. In otherembodiments, the procedures, the processes, and/or the activities ofmethod 200 can be performed in any suitable order. In still otherembodiments, one or more of the procedures, the processes, and/or theactivities of method 200 can be combined or skipped. In someembodiments, method 200 can be performed by financial institution 130(FIG. 1).

Referring to FIG. 2, in some embodiments, method 200 can optionallyinclude one or more preliminary blocks, such as a block 201 and a block202, described below. Specifically, method 200 can include block 201 ofreceiving, at a first financial institution from a mobile device, apreliminary request for account information. The first financialinstitution can be similar or identical to financial institution 130(FIG. 1). The mobile device can be similar or identical to mobile device120 (FIG. 1).

In several embodiments, method 200 additionally can include block 202 ofsending, from the first financial institution to the mobile device, theaccount information. In some embodiments, the account information caninclude an account balance and an account status of a first account. Thefirst account can be similar or identical to one or more of consumeraccounts 131 (FIG. 1).

In a number of embodiments, method 200 further optionally can include ablock 203 of receiving, at a first financial institution from a mobiledevice of a consumer, a first request to pay a merchant for a paymentamount from a first account of the consumer maintained by the firstfinancial institution. The consumer can be similar or identical toconsumer 129 (FIG. 1). The merchant can be similar or identical tomerchant 119 (FIG. 1). In many embodiments, the first request caninclude first information, which can include a merchant identifier, atransaction identifier, and/or the payment amount. In severalembodiments, the first information can be sent to the first financialinstitution from a mobile application running on a mobile device used bythe consumer at a store of the merchant to pay for one or more items tobe purchased from the merchant by the consumer for the payment amount.The mobile application can be similar or identical to mobile application123 (FIG. 1). In some embodiments, the one or more items to be purchasedcan include at least one of one or more products or one or moreservices. In many embodiments, the merchant identifier can be associatedwith the merchant. In a number of embodiments, the mobile applicationcan be associated with the first account. In some embodiments, themerchant identifier can uniquely correspond to a point-of-sale terminalat the store of the merchant. In various embodiments, the merchantidentifier can be obtained by the mobile device from the point-of-saleterminal using a proximity-based wireless data communication protocol.

In many embodiments, method 200 additionally can include a block 204 ofdetermining, at the first financial institution, second information. Inmany embodiments, the second information can include an accountidentifier of a second account of the merchant maintained by a secondfinancial institution, at least partially based on the merchantidentifier and third information obtained from a first system. Thesecond account can be similar or identical to merchant account 151 (FIG.1). The second financial institution can be similar or identical tofinancial institution 150 (FIG. 1). The first system can be similar oridentical to transaction system 140 (FIG. 1). In a number ofembodiments, the account identifier can be or include an account number.In some embodiments, the first system can be in data communication withthe first financial institution and the second financial institution. Inmany embodiments, the first system can be maintained by an entity thatis different from the first financial institution and the secondfinancial institution. In some embodiments, the second informationfurther can include a name of the merchant and/or a location of thestore of the merchant.

In some embodiments, block 204 of determining second informationoptionally can include a block 205 of determining, at the firstfinancial institution, the second information at least partially basedon the merchant identifier and the third information. In a number ofembodiments, the third information can be received by the firstfinancial institution from the first system prior to receiving the firstrequest to pay the merchant from the mobile device. For example, thethird information can be stored at the first financial institution froma previous query to the first system. In many embodiments, the thirdinformation can include the account identifier of the second account. Insome embodiments, the second information can include the thirdinformation.

In other embodiments, block 204 of determining second informationoptionally can include a block 206 and a block 207, described below. Forexample, block 204 can include block 206 of sending, from the firstfinancial institution to the first system, a second request to determinethe second information. In several embodiments, the second request caninclude the merchant identifier.

In these same other embodiments, block 204 can include block 207 ofreceiving, at the first financial institution from the first system, thethird information. The third information can include the accountidentifier of the second account. In many embodiments, the secondinformation can include the third information.

In some embodiments, method 200 can continue after block 204 with ablock 208 of authorizing, at the first financial institution, a paymentfrom the first account to the second account.

In a number of embodiments, block 208 of authorizing the payment fromthe first account to the second account optionally can include blocks209, 210, and 211. Block 209 can include authenticating an identity ofthe consumer that used the mobile device to send the first request topay the merchant from the first account. In some embodiments, block 209of authenticating the identity of the consumer can includeauthenticating the identity of the consumer based at least in part onwhether the mobile device used to send the first request has previouslybeen used by the consumer in transaction involving the first financialinstitution, whether biometrics of the consumer using the mobile devicematch stored biometrics of the consumer, and/or whether at least one ofan identity of the merchant, a location of the merchant, or the paymentamount is consistent with historical patterns of behavior by theconsumer.

In a number of embodiments, the first information further can includethe one or more items to be purchased, and block 209 of authenticatingthe identity of the consumer further can include authenticating theidentity of the consumer based at least in part on the one or more itemsto be purchased by the consumer for the payment amount from themerchant.

In a number of embodiments, block 209 of authenticating the identity ofthe consumer further can include adjusting a level of authentication atleast partially based on the payment amount to be paid to the merchant,whether the mobile device used to send the first request has previouslybeen used by the consumer in transaction involving the first financialinstitution, whether biometrics of the consumer using the mobile devicematch stored biometrics of the consumer, and/or whether at least one ofan identity of the merchant, a location of the merchant, the paymentamount, or the one or more items to be purchased is consistent withhistorical patterns of behavior by the consumer.

In many embodiments, block 210 can include determining a current statusof the first account. For example, the first financial institution candetermine whether the first account is open and in good status, or has afreeze or hold status.

In several embodiments, block 211 can include determining availablefunds of the first account. For example, the first financial institutioncan use the determination of the available funds of the first account todetermine whether the payment amount can be covered by the availablefunds of the first account.

In a number of embodiments, method 200 can continue after block 208 witha block 212 of sending, from the first financial institution to thefirst system, payment information regarding a payment to be made to thesecond account from the first account. In several embodiments, thepayment information can be routed through the first system to the secondfinancial institution such that the second financial institution, uponreceiving the payment information, can notify the merchant in order tosatisfy an expectation of the merchant for payment from the consumer. Insome embodiments, the payment information can include the transactionidentifier, the account identifier of the second account, and/or thepayment amount. In a number of embodiments, the payment information caninclude the merchant identifier.

In some embodiments, the payment information further can include asettlement credit push of funds for the payment amount from the firstaccount to the second account. In other embodiments, the paymentinformation further can include an irrevocable promise to pay thepayment amount from the first account to the second account. In severalembodiments, the payment information further can include a set ofpersonally identifiable information of the consumer. In a number ofembodiments, the set of personally identifiable information can be atleast partially based on privacy instructions sent by the consumer tothe first financial institution.

Turning ahead in the drawings, FIG. 3 illustrates a flow chart for amethod 300, according to an embodiment. In some embodiments, method 300can be a method of facilitating secure payment transactions. Method 300is merely exemplary and is not limited to the embodiments presentedherein. Method 300 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, the procedures, the processes, and/or the activities ofmethod 300 can be performed in the order presented. In otherembodiments, the procedures, the processes, and/or the activities ofmethod 300 can be performed in any suitable order. In still otherembodiments, one or more of the procedures, the processes, and/or theactivities of method 300 can be combined or skipped. In someembodiments, method 300 can be performed by transaction system 140 (FIG.1).

Referring to FIG. 3, method 300 can include a block 301 of receiving, ata first system from a first entity, a request. The first system can besimilar or identical to transaction system 140 (FIG. 1). In someembodiments, the first entity can be a first financial institution. Thefirst financial institution can be similar or identical to financialinstitution 130 (FIG. 1). In other embodiments, the first entity can bea mobile device being used by a consumer. In yet other embodiments, thefirst entity can be a mobile wallet provider in data communication withthe mobile device being used by the consumer. In a number ofembodiments, the request can include a merchant identifier. In severalembodiments, the merchant identifier can be associated with a merchant.The merchant can be similar or identical to merchant 119 (FIG. 1). Inmany embodiments, the first system can be in data communication with thefirst financial institution and a second financial institution. Thesecond financial institution can be similar or identical to financialinstitution 150 (FIG. 1). In various embodiments, the first system canbe maintained by an entity that is different from the first financialinstitution and the second financial institution. In some embodiments,the first financial institution can maintain a first account of aconsumer. The first account can be similar or identical to one or moreof consumer accounts 131 (FIG. 1). The consumer can be similar oridentical to consumer 129 (FIG. 1). In many embodiments, the firstsystem can be in data communication with a merchant account database.The merchant account database can be similar or identical to merchantaccount database 141 (FIG. 1). In a number of embodiments, the firstsystem can include the merchant account database In some embodiments,the first system can include a transaction database. The transactiondatabase can be similar or identical to transaction database 142 (FIG.1). In a number of embodiments, the merchant identifier can uniquelycorrespond to a point-of-sale terminal at the store of the merchant. Invarious embodiments, the merchant identifier can be obtained by themobile device from the point-of-sale terminal using a proximity-basedwireless data communication protocol.

In many embodiments, method 300 additionally can include a block 302 ofdetermining, at the first system, using the merchant account database,first information. In several embodiments, the first information caninclude an account identifier of a second account of the merchantmaintained by a second financial institution. The second account can besimilar or identical to merchant account 151 (FIG. 1). The secondfinancial institution can be similar or identical to financialinstitution 150 (FIG. 1). In some embodiments, the account identifiercan be associated with the merchant identifier in the merchant accountdatabase. In a number of embodiments, the first information further caninclude a name of the merchant and/or a location of a store of themerchant.

In many embodiments, method 300 further can include a block 303 ofsending the first information from the first system to the firstfinancial institution.

In several embodiments, method 300 additionally can include a block 304of receiving, at the first system from the first financial institution,payment information regarding a payment to be made to the second accountfrom the first account to pay the merchant for one or more items to bepurchased from the merchant by the consumer for the payment amount. In anumber of embodiments, the consumer can use a mobile device at the storeof the merchant to pay for the one or more items. The mobile device canbe similar or identical to mobile device 120 (FIG. 1). In someembodiments, the mobile device can be running a mobile applicationassociated with the first account. The mobile application can be similaror identical to mobile application 123 (FIG. 1). In many embodiments,the payment information can include a transaction identifier, theaccount identifier of the second account, and/or the payment amount. Ina number of embodiments, the one or more items to be purchased caninclude at least one of one or more products or one or more services.

In a number of embodiments, method 300 optionally can include a block305 of storing the payment information in the transaction database.

In many embodiments, method 300 can continue after block 304 with ablock 306 of sending, from the first system to the second financialinstitution, the payment information such that the second financialinstitution, upon receiving the payment information, notifies themerchant to satisfy an expectation of the merchant for payment from theconsumer.

In some embodiments, the payment information further can include asettlement credit push of funds for the payment amount from the firstaccount to the second account. In other embodiments, the paymentinformation further can include an irrevocable promise to pay thepayment amount from the first account to the second account. In severalembodiments, the payment information further can include a set ofpersonally identifiable information of the consumer. In a number ofembodiments, the set of personally identifiable information can be atleast partially based on privacy instructions sent by the consumer tothe first financial institution.

Turning ahead in the drawings, FIG. 4 illustrates a flow chart for amethod 400, according to an embodiment. In some embodiments, method 400can be a method of facilitating secure payment transactions. Method 400is merely exemplary and is not limited to the embodiments presentedherein. Method 400 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, the procedures, the processes, and/or the activities ofmethod 400 can be performed in the order presented. In otherembodiments, the procedures, the processes, and/or the activities ofmethod 400 can be performed in any suitable order. In still otherembodiments, one or more of the procedures, the processes, and/or theactivities of method 400 can be combined or skipped. In someembodiments, method 400 can be performed by mobile device 120 (FIG. 1).

Referring to FIG. 4, method 400 can include a block 401 of performing,at a mobile device, a preliminary identity authentication of a consumerusing the mobile device. The mobile device can be similar or identicalto mobile device 120 (FIG. 1). The consumer can be similar or identicalto consumer 129 (FIG. 1).

In many embodiments, method 400 additionally can include a block 402 ofreceiving at the mobile device first information from a point-of-saleterminal. The point-of-sale terminal can be similar or identical topoint-of-sale terminal 110 (FIG. 1). In several embodiments, the firstinformation can include a merchant identifier, a transaction identifier,and/or a payment amount. In some embodiments, the merchant identifiercan uniquely correspond to the point-of-sale terminal at a store of amerchant. The merchant can be similar or identical to merchant 119 (FIG.1). In a number of embodiments, the mobile device can run a mobileapplication that is associated with a first account of the consumerusing the mobile device. The mobile application can be similar oridentical to mobile application 123 (FIG. 1). The first account can besimilar or identical to one or more of consumer accounts 131 (FIG. 1).In several embodiments, the first account of the consumer can bemaintained by a first financial institution. The first financialinstitution can be similar or identical to financial institution 130(FIG. 1).

In some embodiments, method 400 optionally can include various blocksbefore or after block 402 of receiving at the mobile device firstinformation from a point-of-sale terminal. For example, method 400optionally can include a block 403 of sending, from the mobile device tothe first financial institution, a preliminary request for accountinformation. In several embodiments, the account information can includean account balance and an account status of the first account.

In a number of embodiments, method 400 further optionally can include,after block 403 of sending the preliminary request for accountinformation, a block 404 of receiving, at the mobile device from thefirst financial institution, the account information.

In many embodiments, method 400 can continue after block 402 with ablock 405 of sending, from the mobile device to the first financialinstitution, a first request to pay the merchant for the payment amountfrom the first account for one or more items to be purchased from themerchant by the consumer. In a number of embodiments, the first requestcan include the first information, such that the first financialinstitution, upon receiving the first request, can determine secondinformation including an account identifier of a second account of themerchant maintained by a second financial institution, at leastpartially based on the merchant identifier and third informationobtained from a first system, and such that the first financialinstitution can send to the first system payment information regarding apayment to be made to the second account from the first account. Thesecond account can be similar or identical to merchant account 151 (FIG.1). The second financial institution can be similar or identical tofinancial institution 150 (FIG. 1). The first system can be similar oridentical transaction system 140 (FIG. 1).

In a number of embodiments, the payment information can be routedthrough the first system to the second financial institution such thatthe second financial institution, upon receiving the paymentinformation, can notify the merchant to satisfy an expectation of themerchant for payment from the consumer. In several embodiments, thefirst system can be in data communication with the first financialinstitution and the second financial institution. In variousembodiments, the first system can be maintained by an entity that isdifferent from the first financial institution and the second financialinstitution. In a number of embodiments, the payment information caninclude the transaction identifier, the account identifier of the secondaccount, and the payment amount. In some embodiments, the paymentinformation further can include one of: (a) a settlement credit push offunds for the payment amount from the first account to the secondaccount, or (b) an irrevocable promise to pay the payment amount fromthe first account to the second account.

In some embodiments, method 400 optionally can include additional blocksafter sending the first request to pay the merchant and before thepayment information is sent to the first system from the first financialinstitution. For example, in a number of embodiments, after block 405,method 400 optionally can include a block 406 of receiving, at themobile device from the first financial institution, an additionalauthentication request to perform an additional identity authenticationof the consumer using the mobile device.

In various embodiments, method 400 optionally further can include ablock 407 of performing, at the mobile device, the additional identityauthentication of the consumer using the mobile device. In manyembodiments, block 407 can include performing the additionalauthentication of the consumer based at least in part on determiningbiometrics of the consumer using the mobile device and/or requesting theconsumer to enter additional information in the mobile device.

In several embodiments, method 400 optionally and additionally caninclude a block 408 of sending, from the mobile device to the firstfinancial institution, a response to the additional authenticationrequest.

Turning ahead in the drawings, FIG. 5 illustrates a flow chart for amethod 500, according to an embodiment. In some embodiments, method 500can be a method of facilitating secure payment transactions. Method 500is merely exemplary and is not limited to the embodiments presentedherein. Method 500 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, the procedures, the processes, and/or the activities ofmethod 500 can be performed in the order presented. In otherembodiments, the procedures, the processes, and/or the activities ofmethod 500 can be performed in any suitable order. In still otherembodiments, one or more of the procedures, the processes, and/or theactivities of method 500 can be combined or skipped. In someembodiments, method 500 can be performed by point-of-sale terminal 110(FIG. 1).

Referring to FIG. 5, method 500 can include a block 501 of determining,at a point-of-sale terminal at a store of a merchant, a payment amountfor one or more items to be purchased from the merchant by a consumer.The point-of-sale terminal can be similar or identical to point-of-saleterminal 110 (FIG. 1). The merchant can be similar or identical tomerchant 119 (FIG. 1). The consumer can be similar or identical toconsumer 129 (FIG. 1).

In several embodiments, method 500 additionally can include a block 502of sending first information from the point-of-sale terminal to a mobiledevice used by the consumer. The mobile device can be similar oridentical to mobile device 120 (FIG. 1). In a number of embodiments, thefirst information can be sent from the point-of-sale terminal to themobile device using a proximity-based wireless data protocol. In severalembodiments, the first information can include a merchant identifier, atransaction identifier, and/or the payment amount. In a number ofembodiments, the merchant identifier can uniquely correspond to thepoint-of-sale terminal at the store of the merchant. In variousembodiments, the mobile device can run a mobile application that isassociated with a first account of the consumer using the mobile device.The mobile application can be similar or identical to mobile application123 (FIG. 1). The first account can be similar or identical to one ormore of consumer accounts 131 (FIG. 1). In a number of embodiments, thefirst account of the consumer can be maintained by a first financialinstitution. The first financial institution can be similar or identicalto financial institution 130 (FIG. 1). In several embodiments, themobile device, upon receiving the first information, can send a firstrequest to pay the merchant for the payment amount from the firstaccount. In a number of embodiments, the first request can include thefirst information, such that the first financial institution, uponreceiving the first request, can determine second information includingan account identifier of a second account of the merchant maintained bya second financial institution, at least partially based on the merchantidentifier and third information obtained from a first system, and suchthat the first financial institution sends to the first system paymentinformation regarding a payment to be made to the second account fromthe first account. The second account can be similar or identical tomerchant account 151 (FIG. 1). The second financial institution can besimilar or identical to financial institution 150 (FIG. 1). The firstsystem can be similar or identical to transaction system 140 (FIG. 1).

In some embodiments, the payment information can be routed through thefirst system to the second financial institution. In variousembodiments, the first system can be in data communication with thefirst financial institution and the second financial institution. Inmany embodiments, the first system can be maintained by an entity thatis different from the first financial institution and the secondfinancial institution. In several embodiments, the payment informationcan include the transaction identifier, the account identifier of thesecond account, and/or the payment amount. in some embodiments, thepayment information further can include one of: (a) a settlement creditpush of funds for the payment amount from the first account to thesecond account, or (b) an irrevocable promise to pay the payment amountfrom the first account to the second account.

In various embodiments, method 500 optionally can include a block 503 ofreceiving at the point-of-sale terminal from the mobile device,information about the consumer. In some embodiments, block 503 can beperformed before or after block 501 of determining the payment amountfor the one or more items to be purchased from the merchant by theconsumer, before or after block 502 of sending the first informationfrom the point-of-sale terminal to the mobile device used by theconsumer, or before or after block 504, described below.

In many embodiments, method 500 can continue after block 502 with ablock 504 of receiving, at the point-of-sale terminal from the secondfinancial institution, a notification to satisfy an expectation of themerchant for payment from the consumer.

Turning ahead in the drawings, FIG. 6 illustrates a flow chart for amethod 600, according to an embodiment. In some embodiments, method 600can be a method of facilitating secure payment transactions. Method 600is merely exemplary and is not limited to the embodiments presentedherein. Method 600 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, the procedures, the processes, and/or the activities ofmethod 600 can be performed in the order presented. In otherembodiments, the procedures, the processes, and/or the activities ofmethod 600 can be performed in any suitable order. In still otherembodiments, one or more of the procedures, the processes, and/or theactivities of method 600 can be combined or skipped. In someembodiments, method 600 can be performed by financial institution 150(FIG. 1).

Referring to FIG. 6, method 600 can include a block 601 of receiving, ata second financial institution from a first system, payment informationregarding a payment to be made to a second account of a merchantmaintained by the second financial institution from a first account of aconsumer maintained by a first financial institution to pay the merchantfor one or more items to be purchased from the merchant by the consumerfor the payment amount. The second financial institution can be similaror identical to financial institution 150 (FIG. 1). The first system canbe similar or identical to transaction system 140 (FIG. 1). The secondaccount can be similar or identical to merchant account 151 (FIG. 1).The first account can be similar or identical to one or more of consumeraccounts 131 (FIG. 1). The consumer can be similar or identical toconsumer 129 (FIG. 1). The first financial institution can be similar oridentical to financial institution 130 (FIG. 1).

In a number of embodiments, the payment information can be sent from thefirst financial institution to the first system and routed through thefirst system to the second financial institution. In severalembodiments, the first system can be in data communication with thefirst financial institution and the second financial institution. Invarious embodiments, the first system can be maintained by an entitythat is different from the first financial institution and the secondfinancial institution. In many embodiments, the consumer can use amobile device at a store of the merchant to pay for the one or moreitems. The mobile device can be similar or identical to mobile device120 (FIG. 1). In a number of embodiments, the mobile device can run amobile application associated with the first account. The mobileapplication can be similar or identical to mobile application 123 (FIG.1). In several embodiments, the payment information can include atransaction identifier, an account identifier of the second account,and/or the payment amount. In a number of embodiments, the firstfinancial institution can determine the account identifier of the secondaccount based on a merchant identifier and based on third informationobtained from the first system. In several embodiments, the merchantidentifier can uniquely correspond to a point-of-sale terminal at thestore of a merchant. The point-of-sale terminal can be similar oridentical to point-of-sale terminal 110 (FIG. 1).

In a number of embodiments, the mobile device can send a request to paythe merchant for the payment amount from the first account. In manyembodiments, the request can include first information including themerchant identifier, a transaction identifier, and/or the paymentamount. In several embodiments, the payment information further caninclude one of: (a) a settlement credit push of funds for the paymentamount from the first account to the second account, or (b) anirrevocable promise to pay the payment amount from the first account tothe second account.

In several embodiments, method 600 optionally can include a block 602 ofcrediting the second account with the payment amount. For example, afterthe second financial institution has received the payment information,the second account can be credited with the payment amount.

In many embodiments, method 600 can continue after block 601 with ablock 603 of sending, from the second financial institution to thepoint-of-sale terminal, a notification to satisfy an expectation of themerchant for payment from the consumer. In some embodiments, block 603can include notifying the merchant that funds for the payment amount areimmediately available in the second account.

Jumping ahead in the drawings, FIG. 9 illustrates a flow chart for amethod 900, according to an embodiment. In some embodiments, method 900can be a method of facilitating secure payment transactions. Method 900is merely exemplary and is not limited to the embodiments presentedherein. Method 900 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, the procedures, the processes, and/or the activities ofmethod 900 can be performed in the order presented. In otherembodiments, the procedures, the processes, and/or the activities ofmethod 900 can be performed in any suitable order. In still otherembodiments, one or more of the procedures, the processes, and/or theactivities of method 900 can be combined or skipped. In someembodiments, method 900 can be performed by point-of-sale terminal 110(FIG. 1). In some embodiments, method 900 and other blocks in method 900can include using a distributed network including distributed memoryarchitecture to perform the associated activity. This distributedarchitecture can reduce the impact on the network and system resourcesto reduce congestion in bottlenecks while still allowing data to beaccessible from a central location.

Referring to FIG. 9, method 900 can include a block 901 of determining,at a point-of-sale terminal at a store of a merchant, a payment amountfor one or more items to be purchased from the merchant by a consumer ina transaction. The point-of-sale terminal can be similar or identical topoint-of-sale terminal 110 (FIG. 1). The merchant can be similar oridentical to merchant 119 (FIG. 1). The consumer can be similar oridentical to consumer 129 (FIG. 1).

In several embodiments, method 900 also can include a block 902 ofgenerating a transaction code including a merchant public identifier,the payment amount, a transaction identifier for the transaction, and adigital signature. In many embodiments, the transaction code can besimilar or identical to the merchant security transaction code describedabove. In some embodiments, the transaction code can further include oneor more SKUs for the one or more items to be purchased in thetransaction. In some embodiments, the digital signature can be similaror identical to the digital signature described above. In manyembodiments, the merchant public identifier can be similar to themerchant identifier described above. For example, in many embodiments,the merchant identifier can be setup and/or registered through atransaction system, such as transaction system 140 (FIG. 1).

In some embodiments, block 902 of generating a transaction codeincluding a merchant public identifier can include point-of-saleterminal 110 (FIG. 1) cryptographically signing the digital signaturefor the transaction code. In other embodiments, block 902 of generatinga transaction code including a merchant public identifier can includepoint-of-sale terminal 110 (FIG. 1) calling the transaction system, suchas transaction system 140 (FIG. 1), to generate the transaction code.

In a number of embodiments, method 900 additionally can include a block903 of providing the transaction code to a mobile device being used bythe consumer, such that the mobile device verifies the digital signatureand sends a request to pay the merchant for the payment amount from afirst account of the consumer maintained by a first financialinstitution, such that the first financial institution, upon receivingthe request to pay, retrieves from a transaction system an accountidentifier of a second account of the merchant maintained by a secondfinancial institution based on the merchant public identifier, and suchthat the first financial institution sends to the transaction systempayment information regarding a payment to be made to the second accountfrom the first account. The mobile device can be similar or identical tomobile device 120 (FIG. 1). The first account can be similar oridentical to one or more of consumer accounts 131 (FIG. 1). The firstfinancial institution can be similar or identical to financialinstitution 130 (FIG. 1). The second account can be similar or identicalto merchant account 151 (FIG. 1). The second financial institution canbe similar or identical to financial institution 150 (FIG. 1). Thetransaction system can be similar or identical to transaction system 140(FIG. 1). In many embodiments, the transaction system can be maintainedby an entity that is different from the merchant, the first financialinstitution, and the second financial institution. In some embodiments,the payment information can be routed through the transaction system tothe second financial institution. In many embodiments, the paymentinformation can include the transaction identifier, the accountidentifier of the second account, the payment amount, and/or othersuitable information.

In some embodiments, the payment information can include one of: (a) asettlement credit push of funds for the payment amount from the firstaccount to the second account, or (b) an irrevocable promise to pay thepayment amount from the first account to the second account. In manyembodiments, the mobile device can send the request to pay afterreceiving from the consumer an approval for the transaction. Forexample, the consumer can authorize the transaction, after which therequest to pay can be sent from the mobile device.

In many embodiments, block 903 of providing the transaction code to amobile device being used by the consumer can include displaying thetransaction code as a matrix barcode on a screen of the point-of-saleterminal. For example, the transaction code can be displayed as a QRcode on a screen of the point-of-sale terminal, which can be scannedusing a camera of the mobile device. In other embodiments, block 903 ofproviding the transaction code to a mobile device being used by theconsumer can include transmitting the transaction code from thepoint-of-sale terminal to the mobile device using a proximity-basedwireless data communication protocol. In yet other embodiments, thepoint-of-sale terminal can display the transaction code such that it canbe manually input into the mobile device.

In certain embodiments, the first financial institution does not haveaccess to a second account number for the second account for thetransaction, and the second financial institution does not have accessto a first account number for the first account for the transaction. Inother embodiments, the first financial institution can have access to asecond account number for the second account for the transaction, and/orthe second financial institution can have access to a first accountnumber for the first account for the transaction.

In several embodiments, method 900 further can include a block 904 ofreceiving, at the point-of-sale terminal, a notification of payment forthe transaction in real-time while the consumer remains at the store ofthe merchant. In many embodiments, the notification of the payment canbe received by the merchant and/or at the point-of-sale terminal fromthe transaction system. In other embodiments, the notification of thepayment can be received by the merchant and/or at the point-of-saleterminal from the second financial institution system.

Proceeding to the next drawing, FIG. 10 illustrates a flow chart for amethod 1000, according to an embodiment. In some embodiments, method1000 can be a method of facilitating secure payment transactions. Method1000 is merely exemplary and is not limited to the embodiments presentedherein. Method 1000 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, the procedures, the processes, and/or the activities ofmethod 1000 can be performed in the order presented. In otherembodiments, the procedures, the processes, and/or the activities ofmethod 1000 can be performed in any suitable order. In still otherembodiments, one or more of the procedures, the processes, and/or theactivities of method 1000 can be combined or skipped. In someembodiments, method 1000 can be performed by mobile device 120 (FIG. 1)and/or mobile application 123 (FIG. 1).

Referring to FIG. 10, method 1000 can include a block 1001 of receiving,at a mobile device being used by a consumer, a transaction code from apoint-of-sale terminal at a store of a merchant. The mobile device canbe similar or identical to mobile device 120 (FIG. 1). The consumer canbe similar or identical to consumer 129 (FIG. 1). In many embodiments,the transaction code can be similar or identical to the merchantsecurity transaction code described above. The point-of-sale terminalcan be similar or identical to point-of-sale terminal 110 (FIG. 1). Themerchant can be similar or identical to merchant 119 (FIG. 1).

In many embodiments, the transaction code can include a merchant publicidentifier being associated with the merchant, a payment amount for oneor more items to be purchased from the merchant by the consumer in atransaction, a transaction identifier for the transaction, and a digitalsignature. In various embodiments, the transaction code further caninclude one or more SKUs for the one or more items to be purchased inthe transaction. In many embodiments, the merchant public identifier canbe similar to the merchant identifier described above. For example, inmany embodiments, the merchant identifier can be setup and/or registeredthrough a transaction system, such as transaction system 140 (FIG. 1).In some embodiments, the digital signature can be similar or identicalto the digital signature described above. In some embodiments, thedigital signature of the transaction code is cryptographically signed bythe point-of-sale terminal. In other embodiments, the transaction systemcan be called by the point-of-sale terminal to generate the transactioncode.

In some embodiments, block 1001 of receiving, at a mobile device beingused by a consumer, a transaction code from a point-of-sale terminal ata store of a merchant can include using a camera of the mobile device toscan the transaction code as a matrix barcode from a screen of thepoint-of-sale terminal. For example, the transaction code can bedisplayed as a QR code on a screen of the point-of-sale terminal, whichcan be scanned using a camera of the mobile device. In otherembodiments, block 1001 of receiving, at a mobile device being used by aconsumer, a transaction code from a point-of-sale terminal at a store ofa merchant can include receiving the transaction code from thepoint-of-sale terminal using a proximity-based wireless datacommunication protocol. In yet other embodiments, the mobile device canreceive the transaction code through manual input.

In several embodiments, method 1000 also can include a block 1002 ofverifying the digital signature for the transaction code. For example,the digital signature can be verified using a public-key signatureverifying algorithm, as described above, or another suitableverification algorithm.

In a number of embodiments, method 1000 optionally can include a block1003 of receiving an approval for the transaction from the consumerthrough a user interface on the mobile device. For example, the consumercan authorize the transaction, as described above. The user interfacecan be similar to user interface display 1700 (FIG. 17), as describedbelow in further detail.

In several embodiments, method 1000 further can continue after block1002 with a block 1004 of sending, from the mobile device, a request topay the merchant for the payment amount from a first account of theconsumer maintained by a first financial institution, such that thefirst financial institution, upon receiving the request to pay,retrieves from a transaction system an account identifier of a secondaccount of the merchant maintained by a second financial institutionbased on the merchant public identifier, such that the first financialinstitution sends to the transaction system payment informationregarding a payment to be made to the second account from the firstaccount, such that the payment information is routed through thetransaction system to the second financial institution, and such thatthe point-of-sale terminal receives a notification of payment for thetransaction in real-time while the consumer remains at the store of themerchant. In some embodiments, the payment information including thetransaction identifier, the account identifier of the second account,the payment amount, and/or other suitable information.

The first account can be similar or identical to one or more of consumeraccounts 131 (FIG. 1). The first financial institution can be similar oridentical to financial institution 130 (FIG. 1). The transaction systemcan be similar or identical to transaction system 140 (FIG. 1). In manyembodiments, the transaction system can be maintained by an entity thatis different from the merchant, the first financial institution, and thesecond financial institution. The second account can be similar oridentical to merchant account 151 (FIG. 1). The second financialinstitution can be similar or identical to financial institution 150(FIG. 1).

In some embodiments, the payment information can include one of: (a) asettlement credit push of funds for the payment amount from the firstaccount to the second account, or (b) an irrevocable promise to pay thepayment amount from the first account to the second account. In manyembodiments, the notification of the payment can be received at thepoint-of-sale terminal from the transaction system. In otherembodiments, the notification of the payment can be received at thepoint-of-sale terminal from the second financial institution system.

In certain embodiments, the first financial institution does not haveaccess to a second account number for the second account for thetransaction, and the second financial institution does not have accessto a first account number for the first account for the transaction. Inother embodiments, the first financial institution can have access to asecond account number for the second account for the transaction, and/orthe second financial institution can have access to a first accountnumber for the first account for the transaction.

Turning ahead in the drawings, FIG. 11 illustrates a flow chart for amethod 1100, according to an embodiment. In some embodiments, method1100 can be a method of facilitating secure payment transactions. Method1100 is merely exemplary and is not limited to the embodiments presentedherein. Method 1100 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, the procedures, the processes, and/or the activities ofmethod 1100 can be performed in the order presented. In otherembodiments, the procedures, the processes, and/or the activities ofmethod 1100 can be performed in any suitable order. In still otherembodiments, one or more of the procedures, the processes, and/or theactivities of method 1100 can be combined or skipped. In someembodiments, method 1100 can be performed by financial institution 130(FIG. 1). In some embodiments, method 1100 and other blocks in method1100 can include using a distributed network including distributedmemory architecture to perform the associated activity. This distributedarchitecture can reduce the impact on the network and system resourcesto reduce congestion in bottlenecks while still allowing data to beaccessible from a central location.

Referring to FIG. 11, method 1100 can include a block 1101 of receiving,at a first financial institution from a mobile device being used by aconsumer, a request to pay a merchant for a payment amount from a firstaccount of the consumer maintained by the first financial institution.The first financial institution can be similar or identical to financialinstitution 130 (FIG. 1). The mobile device can be similar or identicalto mobile device 120 (FIG. 1). The consumer can be similar or identicalto consumer 129 (FIG. 1). The merchant can be similar or identical tomerchant 119 (FIG. 1). In many embodiments, the first account can besimilar or identical to one or more of consumer accounts 131 (FIG. 1).

In some embodiments, the request to pay can include informationincluding a merchant public identifier, a payment amount for one or moreitems to be purchased from the merchant by the consumer in atransaction, and a transaction identifier for the transaction. In manyembodiments, the merchant public identifier can be similar to themerchant identifier described above. For example, in many embodiments,the merchant identifier can be setup and/or registered through atransaction system, such as transaction system 140 (FIG. 1).

In various embodiments, the mobile device can be used by the consumer ata store of the merchant to pay for the transaction. In a number ofembodiments, the information can be received by the mobile device from apoint-of-sale terminal at the store of the merchant as part of atransaction code. The point-of-sale terminal can be similar or identicalto point-of-sale terminal 110 (FIG. 1). In many embodiments, thetransaction code can be similar or identical to the merchant securitytransaction code described above. In some embodiments, the transactioncode can further include one or more SKUs for the one or more items tobe purchased in the transaction. In several embodiments, the transactioncode can be verified by the mobile device using a digital signature ofthe transaction code. In some embodiments, the digital signature can besimilar or identical to the digital signature described above.

In many embodiments, the mobile device can receive the transaction codeby using a camera on the mobile device to scan the transaction code as amatrix barcode from a screen of the point-of-sale terminal. For example,the transaction code can be displayed as a QR code on a screen of thepoint-of-sale terminal, which can be scanned using a camera of themobile device. In other embodiments, the mobile device can receive thetransaction code using a proximity-based wireless data communicationprotocol. In yet other embodiments, the mobile device can receive thetransaction code through manual input. In some embodiments, the digitalsignature of the transaction code can be cryptographically signed by thepoint-of-sale terminal. In other embodiments, the transaction system canbe called by the point-of-sale terminal to generate the transactioncode.

In a number of embodiments, the request to pay can be received at thefirst financial institution after the mobile device receives from theconsumer an approval for the transaction. For example, the consumer canauthorize the transaction, as described above.

In several embodiments, method 1100 also can include a block 1102 ofretrieving, at the first financial institution from a transactionsystem, an account identifier for a second account of the merchantmaintained by a second financial institution based on the merchantpublic identifier. The transaction system can be similar or identical totransaction system 140 (FIG. 1). In some embodiments, the transactionsystem can be maintained by an entity that is different from themerchant, the first financial institution, and the second financialinstitution. The second account can be similar or identical to merchantaccount 151 (FIG. 1). The second financial institution can be similar oridentical to financial institution 150 (FIG. 1).

In a number of embodiments, method 1100 additionally can include a block1103 of sending, from the first financial institution to the transactionsystem, payment information regarding a payment to be made to the secondaccount from the first account, such that the payment information isrouted through the transaction system to the second financialinstitution, and such that the point-of-sale terminal receives anotification of payment for the transaction in real-time while theconsumer remains at the store of the merchant. In many embodiments, thepayment information can include the transaction identifier, the accountidentifier of the second account, the payment amount, and/or othersuitable information. In several embodiments, the payment informationfurther can include one of: (a) a settlement credit push of funds forthe payment amount from the first account to the second account, or (b)an irrevocable promise to pay the payment amount from the first accountto the second account. In some embodiments, the notification of thepayment can be received at the point-of-sale terminal from thetransaction system. In other embodiments, the notification of thepayment can be received at the point-of-sale terminal from the secondfinancial institution system.

In certain embodiments, the first financial institution does not haveaccess to a second account number for the second account for thetransaction, and the second financial institution does not have accessto a first account number for the first account for the transaction. Inother embodiments, the first financial institution can have access to asecond account number for the second account for the transaction, and/orthe second financial institution can have access to a first accountnumber for the first account for the transaction.

Proceeding to the next drawing, FIG. 12 illustrates a flow chart for amethod 1200, according to an embodiment. In some embodiments, method1200 can be a method of facilitating secure payment transactions. Method1200 is merely exemplary and is not limited to the embodiments presentedherein. Method 1200 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, the procedures, the processes, and/or the activities ofmethod 1200 can be performed in the order presented. In otherembodiments, the procedures, the processes, and/or the activities ofmethod 1200 can be performed in any suitable order. In still otherembodiments, one or more of the procedures, the processes, and/or theactivities of method 1200 can be combined or skipped. In someembodiments, method 1200 can be performed by transaction system 140(FIG. 1). In some embodiments, method 1200 and other blocks in method1200 can include using a distributed network including distributedmemory architecture to perform the associated activity. This distributedarchitecture can reduce the impact on the network and system resourcesto reduce congestion in bottlenecks while still allowing data to beaccessible from a central location.

Referring to FIG. 12, method 1200 can include a block 1201 of receiving,at a transaction system from a first entity, a request including amerchant public identifier associated with a merchant. The transactionsystem can be similar or identical to transaction system 140 (FIG. 1).In many embodiments, the merchant public identifier can be similar tothe merchant identifier described above. For example, in manyembodiments, the merchant identifier can be setup and/or registeredthrough the transaction system. The merchant can be similar or identicalto merchant 119 (FIG. 1). In some embodiments, the first entity can beat least one of the first financial institution, a mobile device beingused by a consumer, or a mobile wallet provider in data communicationwith the mobile device being used by the consumer. For example, thefirst financial institution can be similar or identical to financialinstitution 130 (FIG. 1), the mobile device can be similar or identicalto mobile device 120 (FIG. 1), the consumer can be similar or identicalto consumer 129 (FIG. 1), and/or the mobile wallet provider can besimilar or identical to mobile application 123 (FIG. 1).

In some embodiments, the transaction system can be in data communicationwith a first financial institution that maintains a first account of aconsumer and a second financial institution that maintains a secondaccount of the merchant. The first financial institution can be similaror identical to financial institution 130 (FIG. 1). The first accountcan be similar or identical to one or more of consumer accounts 131(FIG. 1). The consumer can be similar or identical to consumer 129 (FIG.1). The second financial institution can be similar or identical tofinancial institution 150 (FIG. 1). The second account can be similar oridentical to merchant account 151 (FIG. 1). In many embodiments, thetransaction system can be maintained by an entity that is different fromthe merchant, the first financial institution, and the second financialinstitution.

In several embodiments, the consumer can use a mobile device at a storeof the merchant to pay for one or more items in a transaction. Themobile device can be similar or identical to mobile device 120 (FIG. 1).In some embodiments, the mobile device can receive a transaction codefrom a point-of-sale terminal at the store. The point-of-sale terminalcan be similar or identical to point-of-sale terminal 110 (FIG. 1). Inmany embodiments, the transaction code can include a transactionidentifier, a payment amount for the transaction, the merchant publicidentifier, and a digital signature. In many embodiments, thetransaction code can be similar or identical to the merchant securitytransaction code described above. In some embodiments, the transactioncode can further include one or more SKUs for the one or more items tobe purchased in the transaction. In some embodiments, the digitalsignature can be similar or identical to the digital signature describedabove. In some embodiments, the digital certificate of the transactioncode can be cryptographically signed. In many embodiments, thetransaction system can be called by the point-of-sale terminal togenerate the transaction code before the transaction system receives therequest. In a number of embodiments, the transaction code can beverified by the mobile device using a digital signature of thetransaction code.

In some embodiments, the mobile device can receive the transaction codeby using a camera on the mobile device to scan the transaction code as amatrix barcode from a screen of the point-of-sale terminal. For example,the transaction code can be displayed as a QR code on a screen of thepoint-of-sale terminal, which can be scanned using a camera of themobile device. In other embodiments, the mobile device can receive thetransaction code using a proximity-based wireless data communicationprotocol. In yet other embodiments, the mobile device can receive thetransaction code through manual input.

In several embodiments, method 1200 also can include a block 1202 ofdetermining, at the transaction system, an account identifier of thesecond account based on the merchant public identifier using a merchantaccount database. The merchant account database can be similar oridentical to merchant account database 141 (FIG. 1).

In a number of embodiments, method 1200 additionally can include a block1203 of sending the account identifier to the first financialinstitution.

In several embodiments, method 1200 further can include a block 1204 ofreceiving, at the transaction system from the first financialinstitution, payment information regarding a payment to be made to thesecond account from the first account. In some embodiments, the paymentinformation can include the account identifier of the second account,the payment amount, the transaction identifier, and/or other suitableinformation. In many embodiments, the payment information further caninclude one of: (a) a settlement credit push of funds for the paymentamount from the first account to the second account, or (b) anirrevocable promise to pay the payment amount from the first account tothe second account.

In a number of embodiments, method 1200 additionally can include a block1205 of sending, from the transaction system to the second financialinstitution, the payment information, such that the point-of-saleterminal receives a notification of payment for the transaction inreal-time while the consumer remains at the store of the merchant. Inmany embodiments, the notification of the payment can be received at thepoint-of-sale terminal from the transaction system. In otherembodiments, the notification of the payment can be received at thepoint-of-sale terminal from the second financial institution system.

In certain embodiments, the first financial institution does not haveaccess to a second account number for the second account for thetransaction, and the second financial institution does not have accessto a first account number for the first account for the transaction. Inother embodiments, the first financial institution can have access to asecond account number for the second account for the transaction, and/orthe second financial institution can have access to a first accountnumber for the first account for the transaction.

Turning ahead in the drawings, FIG. 13 illustrates a flow chart for amethod 1300, according to an embodiment. In some embodiments, method1300 can be a method of facilitating secure payment transactions. Method1300 is merely exemplary and is not limited to the embodiments presentedherein. Method 1300 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, the procedures, the processes, and/or the activities ofmethod 1300 can be performed in the order presented. In otherembodiments, the procedures, the processes, and/or the activities ofmethod 1300 can be performed in any suitable order. In still otherembodiments, one or more of the procedures, the processes, and/or theactivities of method 1300 can be combined or skipped. In someembodiments, method 1300 can be performed by mobile device 120 (FIG. 1)and/or mobile application 123 (FIG. 1).

Referring to FIG. 13, method 1300 can include a block 1301 ofperforming, at a mobile device being used by a consumer, an identityauthentication of the consumer. The mobile device can be similar oridentical to mobile device 120 (FIG. 1). The consumer can be similar oridentical to consumer 129 (FIG. 1).

In several embodiments, method 1300 also can include a block 1302 ofreceiving, at the mobile device, first information from a point-of-saleterminal at a store of a merchant. The point-of-sale terminal can besimilar or identical to point-of-sale terminal 110 (FIG. 1). Themerchant can be similar or identical to merchant 119 (FIG. 1). In someembodiments, the first information can include a merchant identifier, atransaction identifier, a payment amount, and/or other suitableinformation. In many embodiments, the merchant identifier can beassociated with the merchant. In some embodiments, the payment amountcan be for one or more items to be purchased from the merchant by theconsumer in a transaction. The transaction identifier can be associatedwith the transaction.

In a number of embodiments, method 1300 additionally can include a block1303 of sending, from the mobile device, a request to pay the merchantfor the payment amount from one or more first accounts of the consumermaintained by a first financial institution, such that the firstfinancial institution, upon receiving the request to pay, retrieves froma transaction system an account identifier of a second account of themerchant maintained by a second financial institution based on themerchant identifier, such that the first financial institution sends tothe transaction system payment information regarding a payment to bemade to the second account from the one or more first accounts, suchthat the payment information is routed through the transaction system tothe second financial institution, and such that the point-of-saleterminal receives a notification of payment for the transaction inreal-time while the consumer remains at the store of the merchant. Theone or more first accounts can be similar or identical to one or more ofconsumer accounts 131 (FIG. 1). In several embodiments, the one or morefirst accounts can include at least one non-demand deposit account. Thefirst financial institution can be similar or identical to financialinstitution 130 (FIG. 1). The transaction system can be similar oridentical to transaction system 140 (FIG. 1). In some embodiments, thetransaction system can be maintained by an entity that is different fromthe merchant, the first financial institution, and the second financialinstitution. The second account can be similar or identical to merchantaccount 151 (FIG. 1). The second financial institution can be similar oridentical to financial institution 150 (FIG. 1).

In several embodiments, the payment information can include thetransaction identifier, the account identifier of the second account,the payment amount, and/or other suitable information. In someembodiments, the payment information further can include one of: (a) oneor more settlement credit pushes of funds that collectively total thepayment amount from the one or more first accounts to the secondaccount, or (b) one or more irrevocable promises to pay thatcollectively total the payment amount from the one or more firstaccounts to the second account. In many embodiments, the mobile devicecan send the request to pay after receiving from the consumer anapproval for the transaction. For example, the consumer can authorizethe transaction, after which the request to pay can be sent from themobile device, such as shown in user interface displays 1700 (FIG. 17),as shown described below in further detail.

In many embodiments, the one or more first accounts can include the loanaccount, and in some embodiments, the loan account can be created afterreceiving the first information from the point-of-sale terminal. Inseveral embodiments, the loan account can be used to fund at least afirst portion of the payment amount of the transaction, and in variousembodiments, a second portion of the payment amount can be funded from ademand deposit account of the consumer maintained at the first financialinstitution.

In certain embodiments, the first financial institution does not haveaccess to a second account number for the second account for thetransaction, and the second financial institution does not have accessto a first account number for the first account for the transaction. Inother embodiments, the first financial institution can have access to asecond account number for the second account for the transaction, and/orthe second financial institution can have access to a first accountnumber for the first account for the transaction.

In many embodiments, method 1300 can include one or more optional blocks1304-1308, described below. In some embodiments, one or more of blocks1304-1308 can be performed before block 1303, and in some embodiments,can be performed before block 1302. In the same or other embodiments,one or more of block 1304-1308 can be performed after block 1303.

In several embodiments, method 1300 optionally can include block 1304 ofreceiving, from the first financial institution, an account balance of ademand deposit account of the consumer maintained by the first financialinstitution.

In a number of embodiments, method 1300 optionally can include block1305 of displaying the account balance of the demand deposit account tothe consumer on a user interface of the mobile device. The userinterface can be similar to user interface display 1700 (FIG. 17), asdescribed below in further detail.

In several embodiments, method 1300 optionally can include block 1306 ofdetermining that the account balance of the demand deposit account isless than the payment amount of the transaction. In some embodiments,the determining of block 1306 can involve a comparison in the mobiledevice of the payment account against the account balance. In otherembodiments, another system, such as the first financial institution,can perform the comparison of the payment account against the accountbalance, and the determining of block 1306 can involve receiving, fromthe other system, such as from the first financial institution,information about, or based on, the results of the comparison.

In a number of embodiments, method 1300 optionally can include block1307 of presenting to the consumer an option on a user interface of themobile device to at least partially fund the transaction using the atleast one non-demand deposit account. The user interface can be similarto user interface display 1800 (FIG. 18), user interface display 1900(FIG. 19), and/or user interface display 2000 (FIG. 20), as describedbelow in further detail.

In several embodiments, method 1300 optionally can include block 1308 ofreceiving from the consumer through the user interface a selection to atleast partially fund the payment amount of the transaction using the atleast one non-demand deposit account. The user interface can be similarto user interface display 1800 (FIG. 18), user interface display 1900(FIG. 19), and/or user interface display 2000 (FIG. 20), as describedbelow in further detail. In some embodiments, the one or more firstaccounts further can include the demand deposit account. In manyembodiments, a first portion of the payment amount of the transactioncan be funded from the demand deposit account, and in some embodiments,a second portion of the payment amount of the transaction can be fundedfrom the at least one non-demand deposit account. In other embodiments,the demand deposit account can be devoid of being used to fund thepayment amount of the transaction, and the payment amount of thetransaction can be funded wholly from the at least one non-demanddeposit account.

Turning ahead in the drawings, FIG. 14 illustrates a flow chart for amethod 1400, according to an embodiment. In some embodiments, method1400 can be a method of facilitating secure payment transactions. Method1400 is merely exemplary and is not limited to the embodiments presentedherein. Method 1400 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, the procedures, the processes, and/or the activities ofmethod 1400 can be performed in the order presented. In otherembodiments, the procedures, the processes, and/or the activities ofmethod 1400 can be performed in any suitable order. In still otherembodiments, one or more of the procedures, the processes, and/or theactivities of method 1400 can be combined or skipped. In someembodiments, method 1400 can be performed by financial institution 130(FIG. 1). In some embodiments, method 1400 and other blocks in method1400 can include using a distributed network including distributedmemory architecture to perform the associated activity. This distributedarchitecture can reduce the impact on the network and system resourcesto reduce congestion in bottlenecks while still allowing data to beaccessible from a central location.

Referring to FIG. 14, method 1400 can include a block 1401 of receiving,at a first financial institution from a mobile device being used by aconsumer, a request to pay a merchant for a payment amount from one ormore first accounts of the consumer maintained by the first financialinstitution. The first financial institution can be similar or identicalto financial institution 130 (FIG. 1). The mobile device can be similaror identical to mobile device 120 (FIG. 1). The consumer can be similaror identical to consumer 129 (FIG. 1). The merchant can be similar oridentical to merchant 119 (FIG. 1). The one or more first accounts canbe similar or identical to one or more of consumer accounts 131 (FIG.1). The one or more first accounts can include at least one non-demanddeposit account.

In many embodiments, the request to pay can include informationincluding a merchant identifier, a payment amount for one or more itemsto be purchased from the merchant by the consumer in a transaction, anda transaction identifier for the transaction. In a number ofembodiments, the mobile device can be used by the consumer at a store ofthe merchant to pay for the transaction. In some embodiments, theinformation can be received by the mobile device from a point-of-saleterminal at the store of the merchant. The point-of-sale terminal can besimilar or identical to point-of-sale terminal 110 (FIG. 1).

In various embodiments, the one or more first accounts can include theloan account, and the loan account can be created after receiving therequest to pay the merchant. In the same or other embodiments, the loanaccount can be used to fund at least a first portion of the paymentamount of the transaction, and in a number of embodiments, a secondportion of the payment amount can be funded from a demand depositaccount of the consumer maintained at the first financial institution.

In some embodiments, the at least one non-demand deposit account caninclude a credit account. In a number of embodiments, at least a portionof the payment can be funded from a charge to the credit account. Invarious embodiments, the at least one non-demand deposit account caninclude a points account.

In several embodiments, method 1400 also can include a block 1402 ofretrieving, at the first financial institution from a transactionsystem, an account identifier for a second account of the merchantmaintained by a second financial institution based on the merchantidentifier. The second account can be similar or identical to merchantaccount 151 (FIG. 1). The second financial institution can be similar oridentical to financial institution 150 (FIG. 1). The transaction systemcan be similar or identical to transaction system 140 (FIG. 1). In someembodiments, the transaction system can be maintained by an entity thatis different from the merchant, the first financial institution, and thesecond financial institution.

In a number of embodiments, method 1400 additionally can include a block1403 of sending, from the first financial institution to the transactionsystem, payment information regarding a payment to be made to the secondaccount from the one or more first accounts, such that the paymentinformation is routed through the transaction system to the secondfinancial institution, and such that the point-of-sale terminal receivesa notification of payment for the transaction in real-time while theconsumer remains at the store of the merchant. In many embodiments, thepayment information can include the transaction identifier, the accountidentifier of the second account, the payment amount, and/or othersuitable include. In some embodiments, the payment information furthercan include one of: (a) one or more settlement credit pushes of fundsthat collectively total the payment amount from the one or more firstaccounts to the second account, or (b) one or more irrevocable promisesto pay that collectively total the payment amount from the one or morefirst accounts to the second account. In many embodiments, the mobiledevice can send the request to pay after receiving from the consumer anapproval for the transaction. For example, the consumer can authorizethe transaction, after which the request to pay can be sent from themobile device, such as shown in user interface display 1700 (FIG. 17),as shown described below in further detail.

In certain embodiments, the first financial institution does not haveaccess to a second account number for the second account for thetransaction, and the second financial institution does not have accessto a first account number for the first account for the transaction. Inother embodiments, the first financial institution can have access to asecond account number for the second account for the transaction, and/orthe second financial institution can have access to a first accountnumber for the first account for the transaction.

In many embodiments, method 1400 can include one or more optional blocks1404-1407, described below. In some embodiments, one or more of blocks1404-1407 can be performed before one or more of blocks 1401-1403. Inthe same or other embodiments, one or more of blocks 1404-1407 can beperformed after block 1403.

In several embodiments, method 1400 optionally can include block 1404 ofsending, to the mobile device, an account balance of a demand depositaccount of the consumer maintained by the first financial institution.For example, the account balance can be displayed on the mobile deviceon a user interface, such as shown in user interface display 1700 (FIG.17), as shown described below in further detail.

In a number of embodiments, method 1400 optionally can include block1405 of determining that the account balance of the demand depositaccount is less than the payment amount of the transaction.

In several embodiments, method 1400 optionally can include block 1406 ofsending, to the mobile device, an option to at least partially fund thetransaction using the at least one non-demand deposit account. Forexample, the option can be displayed on the mobile device using a userinterface, such as shown in user interface display 1800 (FIG. 18), userinterface display 1900 (FIG. 19), and/or user interface display 2000(FIG. 20), as described below in further detail.

In a number of embodiments, method 1400 optionally can include block1407 of receiving, from the mobile device, a selection to at leastpartially fund the payment amount of the transaction using the at leastone non-demand deposit account. For example, the selection can bereceived on the mobile device through a user interface, such as shown inuser interface display 1800 (FIG. 18), user interface display 1900 (FIG.19), and/or user interface display 2000 (FIG. 20), as described below infurther detail. In many embodiments, the one or more first accountsfurther can include the demand deposit account. In some embodiments, afirst portion of the payment amount of the transaction can be fundedfrom the demand deposit account, and a second portion of the paymentamount of the transaction can be funded from the at least one non-demanddeposit account. In other embodiments, the demand deposit account can bedevoid of being used to fund the payment amount of the transaction, andthe payment amount of the transaction can be funded wholly from the atleast one non-demand deposit account.

Turning ahead in the drawings, FIG. 15 illustrates a flow chart for amethod 1500, according to an embodiment. In some embodiments, method1500 can be a method of facilitating secure payment transactions. Method1500 is merely exemplary and is not limited to the embodiments presentedherein. Method 1500 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, the procedures, the processes, and/or the activities ofmethod 1500 can be performed in the order presented. In otherembodiments, the procedures, the processes, and/or the activities ofmethod 1500 can be performed in any suitable order. In still otherembodiments, one or more of the procedures, the processes, and/or theactivities of method 1500 can be combined or skipped. In someembodiments, method 1500 can be performed by transaction system 140(FIG. 1). In some embodiments, method 1500 and other blocks in method1500 can include using a distributed network including distributedmemory architecture to perform the associated activity. This distributedarchitecture can reduce the impact on the network and system resourcesto reduce congestion in bottlenecks while still allowing data to beaccessible from a central location.

Referring to FIG. 15, method 1500 can include a block 1501 of receiving,at a transaction system from a first entity, a request including amerchant identifier associated with a merchant. The transaction systemcan be similar or identical to transaction system 140 (FIG. 1). In manyembodiments, the merchant identifier can be similar to the merchantidentifier described above. For example, in many embodiments, themerchant identifier can be setup and/or registered through thetransaction system. The merchant can be similar or identical to merchant119 (FIG. 1). In some embodiments, the first entity can be at least oneof the first financial institution, a mobile device being used by aconsumer, or a mobile wallet provider in data communication with themobile device being used by the consumer. For example, the firstfinancial institution can be similar or identical to financialinstitution 130 (FIG. 1), the mobile device can be similar or identicalto mobile device 120 (FIG. 1), the consumer can be similar or identicalto consumer 129 (FIG. 1), and/or the mobile wallet provider can besimilar or identical to mobile application 123 (FIG. 1) and/or mobilewallet provider 160 (FIG. 1).

In some embodiments, the transaction system can be in data communicationwith a first financial institution that maintains one or more firstaccounts of a consumer and a second financial institution that maintainsa second account of the merchant. The first financial institution can besimilar or identical to financial institution 130 (FIG. 1). The one ormore first accounts can be similar or identical to one or more ofconsumer accounts 131 (FIG. 1). In many embodiments, the one or morefirst accounts can include one or more of at least one non-demanddeposit account. The consumer can be similar or identical to consumer129 (FIG. 1). The second financial institution can be similar oridentical to financial institution 150 (FIG. 1). The second account canbe similar or identical to merchant account 151 (FIG. 1). In manyembodiments, the transaction system can be maintained by an entity thatis different from the merchant, the first financial institution, and thesecond financial institution. In several embodiments, the consumer canuse a mobile device at a store of the merchant to pay a payment amountfor one or more items in a transaction using the one or more firstaccounts. The mobile device can be similar or identical to mobile device120 (FIG. 1).

In several embodiments, the first financial institution can beconfigured to send to the mobile device an account balance of a demanddeposit account of the consumer maintained by the first financialinstitution. For example, the account balance can be displayed on themobile device on a user interface, such as shown in user interfacedisplay 1700 (FIG. 17), as shown described below in further detail.

In some embodiments, the first financial institution can be configuredto determine that the account balance of the demand deposit account isless than the payment amount of the transaction.

In many embodiments, the first financial institution can be configuredto send to the mobile device an option to at least partially fund thetransaction using the at least one non-demand deposit account. Forexample, the option can be displayed on the mobile device using a userinterface, such as shown in user interface display 1800 (FIG. 18), userinterface display 1900 (FIG. 19), and/or user interface display 2000(FIG. 20), as described below in further detail.

In a number of embodiments, the first financial institution can beconfigured to receive from the mobile device a selection to at leastpartially fund the payment amount of the transaction using the at leastone non-demand deposit account. For example, the selection can bereceived on the mobile device through a user interface, such as shown inuser interface display 1800 (FIG. 18), user interface display 1900 (FIG.19), and/or user interface display 2000 (FIG. 20), as described below infurther detail. In many embodiments, the one or more first accountsfurther can include the demand deposit account. In some embodiments, afirst portion of the payment amount of the transaction can be fundedfrom the demand deposit account, and a second portion of the paymentamount of the transaction can be funded from the at least one non-demanddeposit account. In other embodiments, the demand deposit account can bedevoid of being used to fund any portion of the payment amount of thetransaction, and the payment amount of the transaction can be fundedwholly from the at least one non-demand deposit account.

In various embodiments, the one or more first accounts can include theloan account, and the loan account can be created after the consumerauthorizes paying the payment amount. In the same or other embodiments,the loan account can be used to fund at least a first portion of thepayment amount of the transaction, and in a number of embodiments, asecond portion of the payment amount can be funded from a demand depositaccount or another non-demand deposit account of the consumer maintainedat the first financial institution.

In some embodiments, the at least one non-demand deposit account caninclude a credit account. In a number of embodiments, at least a portionof the payment can be funded from a charge to the credit account. Invarious embodiments, the at least one non-demand deposit account caninclude a points account.

In several embodiments, method 1500 also can include a block 1502 ofdetermining, at the transaction system, an account identifier of thesecond account of the merchant maintained by a second financialinstitution using a merchant account database. The merchant accountdatabase can be similar or identical to merchant account database 141(FIG. 1).

In a number of embodiments, method 1500 additionally can include a block1503 of sending the account identifier from the transaction system tothe first financial institution.

In several embodiments, method 1500 further can include a block 1504 ofreceiving, at the transaction system from the first financialinstitution, payment information regarding a payment to be made to thesecond account from the one or more first accounts. In some embodiments,the payment information can include a transaction identifier, theaccount identifier of the second account, the payment amount, and/orother suitable information. In many embodiments, the payment informationfurther can include one or more of: (a) one or more settlement creditpushes of funds that collectively total the payment amount from the oneor more first accounts to the second account, or (b) one or moreirrevocable promises to pay that collectively total the payment amountfrom the one or more first accounts to the second account. In manyembodiments, the mobile device can send the request to pay afterreceiving from the consumer an approval for the transaction. Forexample, the consumer can authorize the transaction, after which therequest to pay can be sent from the mobile device, such as shown in userinterface display 1700 (FIG. 17), as shown described below in furtherdetail.

In a number of embodiments, method 1500 additionally can include a block1505 of sending, from the transaction system to the second financialinstitution, the payment information, such that a point-of-sale terminalat the store of the merchant receives a notification of payment for thetransaction in real-time while the consumer remains at the store of themerchant. The point-of-sale terminal can be similar or identical topoint-of-sale terminal 110 (FIG. 1). In many embodiments, thenotification of the payment can be received at the point-of-saleterminal from the transaction system. In other embodiments, thenotification of the payment can be received at the point-of-saleterminal from the second financial institution system.

In certain embodiments, the first financial institution does not haveaccess to a second account number for the second account for thetransaction, and the second financial institution does not have accessto a first account number for the first account for the transaction. Inother embodiments, the first financial institution can have access to asecond account number for the second account for the transaction, and/orthe second financial institution can have access to a first accountnumber for the first account for the transaction.

Proceeding to the next drawing, FIG. 16 illustrates a flow chart for amethod 1600, according to an embodiment. In some embodiments, method1600 can be a method of facilitating secure payment transactions. Method1600 is merely exemplary and is not limited to the embodiments presentedherein. Method 1600 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, the procedures, the processes, and/or the activities ofmethod 1600 can be performed in the order presented. In otherembodiments, the procedures, the processes, and/or the activities ofmethod 1600 can be performed in any suitable order. In still otherembodiments, one or more of the procedures, the processes, and/or theactivities of method 1600 can be combined or skipped. In someembodiments, method 1600 can be performed by point-of-sale terminal 110(FIG. 1). In some embodiments, method 1600 and other blocks in method1600 can include using a distributed network including distributedmemory architecture to perform the associated activity. This distributedarchitecture can reduce the impact on the network and system resourcesto reduce congestion in bottlenecks while still allowing data to beaccessible from a central location.

Referring to FIG. 16, method 1600 can include a block 1601 ofdetermining, at a point-of-sale terminal at a store of a merchant, apayment amount for one or more items to be purchased from the merchantby a consumer in a transaction. The point-of-sale terminal can besimilar or identical to point-of-sale terminal 110 (FIG. 1). Themerchant can be similar or identical to merchant 119 (FIG. 1). Theconsumer can be similar or identical to consumer 129 (FIG. 1).

In several embodiments, method 1600 also can include a block 1602 ofsending first information from the point-of-sale terminal to a mobiledevice used by the consumer. The mobile device can be similar oridentical to mobile device 120 (FIG. 1). In many embodiments, the firstinformation can include a merchant identifier, a transaction identifier,and the payment amount. In many embodiments, the merchant identifier canbe similar to the merchant identifier described above. For example, inmany embodiments, the merchant identifier can be setup and/or registeredthrough a transaction system, such as transaction system 140 (FIG. 1).In many embodiments, the mobile device can send a request to pay themerchant for the payment amount from one or more first accounts of theconsumer maintained by a first financial institution. The firstfinancial institution can be similar or identical to financialinstitution 130 (FIG. 1). The one or more first accounts can be similaror identical to one or more of consumer accounts 131 (FIG. 1). In manyembodiments, the one or more first accounts can include one or more ofat least one non-demand deposit account. In a number of embodiments, thefirst financial institution, upon receiving the request to pay, canretrieve from a transaction system an account identifier of a secondaccount of the merchant maintained by a second financial institutionbased on the merchant identifier. The second financial institution canbe similar or identical to financial institution 150 (FIG. 1). Thesecond account can be similar or identical to merchant account 151 (FIG.1). The transaction system can be similar or identical to transactionsystem 140 (FIG. 1). In some embodiment, the first financial institutioncan send to the transaction system payment information regarding apayment to be made to the second account from the one or more firstaccounts, such that the payment information can be routed through thetransaction system to the second financial institution. In a number ofembodiments, the payment information can include the transactionidentifier, the account identifier of the second account, the paymentamount, and/or other suitable information. In many embodiments, thetransaction system can be maintained by an entity that is different fromthe merchant, the first financial institution, and the second financialinstitution.

In some embodiments, the payment information further includes one ormore of: (a) one or more settlement credit pushes of funds thatcollectively total the payment amount from the one or more firstaccounts to the second account, or (b) one or more irrevocable promisesto pay that collectively total the payment amount from the one or morefirst accounts to the second account. In many embodiments, the mobiledevice can send the request to pay after receiving from the consumer anapproval for the transaction. For example, the consumer can authorizethe transaction, after which the request to pay can be sent from themobile device. For example, the consumer can authorize the transaction,after which the request to pay can be sent from the mobile device, suchas shown in user interface display 1700 (FIG. 17), as shown describedbelow in further detail.

In several embodiments, the first financial institution can beconfigured to send to the mobile device an account balance of a demanddeposit account of the consumer maintained by the first financialinstitution. For example, the account balance can be displayed on themobile device on a user interface, such as shown in user interfacedisplay 1700 (FIG. 17), as shown described below in further detail.

In some embodiments, the first financial institution can be configuredto determine that the account balance of the demand deposit account isless than the payment amount of the transaction.

In many embodiments, the first financial institution can be configuredto send to the mobile device an option to at least partially fund thetransaction using the at least one non-demand deposit account. Forexample, the option can be displayed on the mobile device using a userinterface, such as shown in user interface display 1800 (FIG. 18), userinterface display 1900 (FIG. 19), and/or user interface display 2000(FIG. 20), as described below in further detail.

In a number of embodiments, the first financial institution can beconfigured to receive from the mobile device a selection to at leastpartially fund the payment amount of the transaction using the at leastone non-demand deposit account. For example, the selection can bereceived on the mobile device through a user interface, such as shown inuser interface display 1800 (FIG. 18), user interface display 1900 (FIG.19), and/or user interface display 2000 (FIG. 20), as described below infurther detail. In many embodiments, the one or more first accountsfurther can include the demand deposit account. In some embodiments, afirst portion of the payment amount of the transaction can be fundedfrom the demand deposit account, and a second portion of the paymentamount of the transaction can be funded from the at least one non-demanddeposit account. In other embodiments, the demand deposit account can bedevoid of being used to fund any portion of the payment amount of thetransaction, and the payment amount of the transaction can be fundedwholly from the at least one non-demand deposit account.

In various embodiments, the one or more first accounts can include theloan account, and the loan account can be created after receiving therequest to pay the merchant. In the same or other embodiments, the loanaccount can be used to fund at least a first portion of the paymentamount of the transaction, and in a number of embodiments, a secondportion of the payment amount can be funded from a demand depositaccount or another non-demand deposit account of the consumer maintainedat the first financial institution.

In some embodiments, the at least one non-demand deposit account caninclude a credit account. In a number of embodiments, at least a portionof the payment can be funded from a charge to the credit account. Invarious embodiments, the at least one non-demand deposit account caninclude a points account.

In certain embodiments, the first financial institution does not haveaccess to a second account number for the second account for thetransaction, and the second financial institution does not have accessto a first account number for the first account for the transaction. Inother embodiments, the first financial institution can have access to asecond account number for the second account for the transaction, and/orthe second financial institution can have access to a first accountnumber for the first account for the transaction.

In several embodiments, method 1600 further can include a block 1603 ofreceiving, at the point-of-sale terminal, a notification of payment forthe transaction in real-time while the consumer remains at the store ofthe merchant. In many embodiments, the notification of the payment canbe received by the merchant and/or at the point-of-sale terminal fromthe transaction system. In other embodiments, the notification of thepayment can be received by the merchant and/or at the point-of-saleterminal from the second financial institution system.

Turning ahead in the drawings, FIG. 17 illustrates an exemplary userinterface display 1700 to allow a consumer (e.g., 129 (FIG. 1)) toapprove a transaction on a mobile device (e.g., 120 (FIG. 1)). Userinterface display 1700 is merely exemplary, and embodiments of the userinterface display are not limited to the embodiments presented herein.The user interface display can be employed in many different embodimentsor examples not specifically depicted or described herein, and caninclude other suitable elements. In many embodiments, mobile application123 (FIG. 1) can provide an interface for display on mobile device 120(FIG. 1), which can include user interface display 1700. In a number ofembodiments, the interface can allow consumer 129 (FIG. 1) to approve ordecline a transaction request received from point-of-sale terminal 110(FIG. 1).

In a number of embodiments, user interface display 1700 can include atitle bar 1701, a descriptor 1710, a payment amount field 1720, amerchant field 1730, a transaction identifier field 1740, a prompt 1750,an approving selection button 1760, and/or a declining selection button1770. In many embodiments, title bar 1701 can include the name of themobile wallet or mobile application (e.g., mobile application 123 (FIG.1)). In a number of embodiments, descriptor 1710 can describe that atransaction request was received. For example, after mobile device 120(FIG. 1) receives information, such as the transaction code, themerchant identifier, the payment amount, the transaction identifier,and/or other information from point-of-sale terminal 110 (FIG. 1), thenuser interface display 1700 can be displayed on mobile device 120(FIG. 1) to consumer 129 (FIG. 1).

In several embodiments, user interface display 1700 can include a numberof fields to display information about the transaction, such as paymentamount field 1720, merchant field 1730, and/or transaction identifierfield 1740. In many embodiments, payment amount field 1720 can displaythe payment amount received from point-of-sale terminal 110 (FIG. 1). Inseveral embodiments, merchant field 1730 can display the name ofmerchant 119 (FIG. 1). In some embodiments, the name of the merchant canbe received from point-of-sale terminal 110 (FIG. 1). In otherembodiment, the merchant identifier received from point-of-sale terminal110 (FIG. 1) can be used to retrieve the name of the merchant, such asby mobile device 120 (FIG. 1) querying transaction system 140 (FIG. 1)directly or through mobile wallet provider 160 (FIG. 1) and/or financialinstitution 130 (FIG. 1). In a number of embodiments, transactionidentifier field 1740 can display the transaction identifier receivedfrom point-of-sale terminal 110 (FIG. 1). In other embodiments, userinterface display 1700 can include additional or other suitable fieldsto display information about the transaction.

In several embodiments, prompt 1750 can ask consumer 129 (FIG. 1) toconfirm the transaction using an account (e.g., consumer account 131(FIG. 1)) that has been provisioned to or otherwise associated withmobile application 123 (FIG. 1), such as Checking Account A. When morethan one account (e.g., consumer account 131 (FIG. 1)) has beenprovisioned to or otherwise associated with mobile application 123 (FIG.1), the user interface display (e.g., 1700) can include a request toselect one of the accounts (e.g., consumer account 131 (FIG. 1)) to usefor the payment transaction. In many embodiments, approving selectionbutton 1760 can be selected by consumer 129 (FIG. 1) to approve thetransaction using the account. In some embodiments, declining selectionbutton 1770 can be selected by consumer 129 (FIG. 1) to decline thetransaction using the account.

Proceeding to the next drawing, FIG. 18 illustrates an exemplary userinterface display 1800 to allow a consumer (e.g., 129 (FIG. 1)) tochoose to use another account for the payment transaction when theapproved account has insufficient funds or limited funds. User interfacedisplay 1800 is merely exemplary, and embodiments of the user interfacedisplay are not limited to the embodiments presented herein. The userinterface display can be employed in many different embodiments orexamples not specifically depicted or described herein, and can includeother suitable elements. User interface display 1800 can be similar touser interface display 1700 (FIG. 17), and various elements of userinterface display 1800 can be similar or identical to various elementsof user interface display 1700 (FIG. 17). In many embodiments, mobileapplication 123 (FIG. 1) can provide an interface for display on mobiledevice 120 (FIG. 1), which can include user interface display 1800. In anumber of embodiments, the interface can allow consumer 129 (FIG. 1) tochoose whether to use another account for the payment transaction whenthe approved account has insufficient or limited funds.

In a number of embodiments, user interface display 1800 can include atitle bar 1801, an account balance field 1810, a payment amount field1820, a prompt 1830, an account selection button 1840, and/or acanceling selection button 1850. In many embodiments, title bar 1801 caninclude the name of the mobile wallet or mobile application (e.g.,mobile application 123 (FIG. 1)). Title bar 1801 can be similar oridentical to title bar 1701 (FIG. 17).

In several embodiments, user interface display 1800 can include a numberof fields to display information about the transaction request using theaccount approved in user interface display 1700 (FIG. 17). For example,the fields can include account balance field 1810 and payment amountfield 1820. In some embodiments, account balance field can show thebalance of the account that was approved for payment using userinterface display 1700 (FIG. 17). In many embodiments, payment amountfield 1820 can display the payment amount. Payment amount field 1820 canbe similar or identical to payment amount field 1720 (FIG. 17). In manyembodiments, user interface display 1800 can be displayed when theaccount balance is less than the payment amount. In other embodiments,user interface display 1800 can be displayed when the account balance ismore than the payment amount, but the difference between the accountbalance and the payment amount is less than a threshold amount, such as$10, $50, $100, $500, or another suitable threshold amount.

In several embodiments, prompt 1830 can ask consumer 129 (FIG. 1)whether to use another account or loan to pay for the payment amount. Inmany embodiments, account selection button 1840 can be selected byconsumer 129 (FIG. 1) to indicate that another account or loan should beused to at least partially pay for the payment amount. In someembodiments, canceling selection button 1850 can be selected by consumer129 (FIG. 1) to cancel the transaction. In some embodiments, such aswhen the account balance is sufficient to cover the payment amount,another selection button (not shown) can be included in the userinterface display (e.g., 1800) to authorize proceeding with the paymenttransaction using the account approved in user interface display 1700(FIG. 17).

Proceeding to the next drawing, FIG. 19 illustrates an exemplary userinterface display 1900 to allow a consumer (e.g., 129 (FIG. 1)) toselect another account for the payment transaction when the approvedaccount has insufficient funds. User interface display 1900 is merelyexemplary, and embodiments of the user interface display are not limitedto the embodiments presented herein. The user interface display can beemployed in many different embodiments or examples not specificallydepicted or described herein, and can include other suitable elements.User interface display 1900 can be similar to user interface display1700 (FIG. 17) and/or user interface display 1800 (FIG. 18), and variouselements of user interface display 1900 can be similar or identical tovarious elements of user interface display 1700 (FIG. 17) and/or userinterface display 1800 (FIG. 18). In many embodiments, mobileapplication 123 (FIG. 1) can provide an interface for display on mobiledevice 120 (FIG. 1), which can include user interface display 1900. In anumber of embodiments, the interface can allow consumer 129 (FIG. 1) toselect another account for the payment transaction when the approvedaccount has insufficient or limited funds.

In a number of embodiments, user interface display 1900 can include atitle bar 1901, a prompt 1910, an option 1911, an option 1912, an option1913, an option 1914, a proceeding selection button 1920, and/or acanceling selection button 1930. In many embodiments, title bar 1901 caninclude the name of the mobile wallet or mobile application (e.g.,mobile application 123 (FIG. 1)). Title bar 1901 can be similar oridentical to title bar 1701 (FIG. 17) and/or title bar 1801 (FIG. 18).

In many embodiments, prompt 1910 can ask consumer 129 (FIG. 1) to selectanother account or loan to use for the payment transaction. In variousembodiments, user interface display 1900 can include one or more optionsof other accounts or loan options that the user can select, such asoptions 1911-1914. In some embodiments, the options can include one ormore existing accounts, such as Savings Account B displayed in option1911, Credit Account C displayed in option 1912, and Points Account Ddisplayed in option 1914. For example, Savings Account B, Credit AccountC, and/or Points Account D can be others of consumer accounts 131(FIG. 1) held by consumer 129 (FIG. 1) at financial institution 130(FIG. 1). In a number of embodiments, the options can include theopportunity to open a new loan, as displayed in option 1913. Forexample, the new loan can be a micro-loan to pay at least partially forthe payment amount, as described above. In some embodiments, userinterface display 1900 can allow consumer 129 (FIG. 1) to select one ofoptions 1911-1914. In other embodiments, user interface display 1900 canallowed consumer 129 (FIG. 1) to select more than one of options1911-1914.

In many embodiments, proceeding selection button 1920 can be selected byconsumer 129 (FIG. 1) to indicate that accounts corresponding to the oneor more options (e.g., 1911-1914) should be used for the paymenttransaction. In some embodiments, canceling selection button 1930 can beselected by consumer 129 (FIG. 1) to cancel the transaction.

Proceeding to the next drawing, FIG. 20 illustrates an exemplary userinterface display 2000 to allow a consumer (e.g., 129 (FIG. 1)) toselect the amount to pay using the other account selected in userinterface display 1900 (FIG. 19). User interface display 2000 is merelyexemplary, and embodiments of the user interface display are not limitedto the embodiments presented herein. The user interface display can beemployed in many different embodiments or examples not specificallydepicted or described herein, and can include other suitable elements.User interface display 2000 can be similar to user interface display1700 (FIG. 17), user interface display 1800 (FIG. 18), and/or userinterface display 1900 (FIG. 19), and various elements of user interfacedisplay 2000 can be similar or identical to various elements of userinterface display 1700 (FIG. 17), user interface display 1800 (FIG. 18),and/or user interface display 1900 (FIG. 19). In many embodiments,mobile application 123 (FIG. 1) can provide an interface for display onmobile device 120 (FIG. 1), which can include user interface display2000. In a number of embodiments, the interface can allow consumer 129(FIG. 1) to select the amount to pay using the other account selected inuser interface display 1900 (FIG. 19).

In a number of embodiments, user interface display 2000 can include atitle bar 2001, a prompt 2010, an option 2011, an option 2012, anapproving selection button 2020, and/or a canceling selection button2030. In many embodiments, title bar 2001 can include the name of themobile wallet or mobile application (e.g., mobile application 123 (FIG.1)). Title bar 2001 can be similar or identical to title bar 1701 (FIG.17), title bar 1801 (FIG. 18), and/or title bar 1901 (FIG. 19).

In many embodiments, prompt 2010 can ask consumer 129 (FIG. 1) to selectthe amount to pay using the other account or payment option selected inuser interface display 1900 (FIG. 19), such as a new loan. In variousembodiments, user interface display 2000 can include one or more optionsthat consumer 129 (FIG. 1) can select, such as options 2011-2012. Forexample, option 2011 can include the option to pay the full paymentamount using the other account (e.g., new loan) selected in userinterface display 1900 (FIG. 19). As another example, option 2012 caninclude the option to partially pay the payment amount using the otheraccount (e.g., new loan) selected in user interface display 1900 (FIG.19), and can allow consumer 129 (FIG. 1) to enter the amount to be usedfor the partial payment from the other account. When more than oneaccount was selected using user interface display 1900 (FIG. 19), theuser interface display (e.g., 2000) can include a prompt (e.g., 2010)and options (e.g., 2011-2012) for each of the other accounts selected inuser interface display 1900 (FIG. 19). In many embodiments, only one ofoptions 2011 and 2012 can be selected, per account, by consumer 129(FIG. 1) and approved by consumer 129 (FIG. 1) via approving selectionbutton 2020.

In many embodiments, approving selection button 2020 can be selected byconsumer 129 (FIG. 1) to indicate that amount selected in one of options2011-2012 should be used to pay for the payment transaction. In someembodiments, canceling selection button 2030 can be selected by consumer129 (FIG. 1) to cancel the transaction.

Proceeding to the next drawing, FIG. 21 illustrates an exemplary userinterface display 2100 to confirm that a payment request has been sentfrom mobile device 120 (FIG. 1). User interface display 2100 is merelyexemplary, and embodiments of the user interface display are not limitedto the embodiments presented herein. The user interface display can beemployed in many different embodiments or examples not specificallydepicted or described herein, and can include other suitable elements.User interface display 2100 can be similar to user interface display1700 (FIG. 17), user interface display 1800 (FIG. 18), user interfacedisplay 1900 (FIG. 19), and/or user interface display 2000 (FIG. 20),and various elements of user interface display 2100 can be similar oridentical to various elements of user interface display 1700 (FIG. 17),user interface display 1800 (FIG. 18), user interface display 1900 (FIG.19), and/or user interface display 2000 (FIG. 20). In many embodiments,mobile application 123 (FIG. 1) can provide an interface for display onmobile device 120 (FIG. 1), which can include user interface display2100. In a number of embodiments, the interface can display aconfirmation to consumer 129 (FIG. 1) that a request has been sent forthe payment authorized in user interface display 1700 (FIG. 17), userinterface display 1800 (FIG. 18), user interface display 1900 (FIG. 19),and/or user interface display 2000 (FIG. 20).

In a number of embodiments, user interface display 2100 can include atitle bar 2101, a descriptor field 2110, and/or a selection button 2120.In many embodiments, title bar 2101 can include the name of the mobilewallet or mobile application (e.g., mobile application 123 (FIG. 1)).Title bar 2101 can be similar or identical to title bar 1701 (FIG. 17),title bar 1801 (FIG. 18), title bar 1901 (FIG. 19), and/or title bar2001 (FIG. 20).

In many embodiments, descriptor field 2110 can include information aboutthe payment that was requested, such as the amount that was requested tobe paid out of each of the accounts that were authorized for payment byconsumer 129 (FIG. 1). For example, if consumer 129 (FIG. 1) choose topartially pay for the payment amount using a new loan in the amount of$83.20, then descriptor field 2110 can display that $60.00 from AccountA was used and $83.20 from New Loan was used, as shown in FIG. 21.

In several embodiments, selection button 2120 can be selected byconsumer 129 (FIG. 1) to dismiss the message displayed in user interfacedisplay 2100.

Proceeding to the next drawing, FIG. 22 illustrates an exemplary userinterface display 2200 to confirm that payment transaction to merchant119 (FIG. 1) has successfully completed. User interface display 2200 ismerely exemplary, and embodiments of the user interface display are notlimited to the embodiments presented herein. The user interface displaycan be employed in many different embodiments or examples notspecifically depicted or described herein, and can include othersuitable elements. User interface display 2200 can be similar to userinterface display 1700 (FIG. 17), user interface display 1800 (FIG. 18),user interface display 1900 (FIG. 19), user interface display 2000 (FIG.20), and/or user interface display 2100 (FIG. 21), and various elementsof user interface display 2200 can be similar or identical to variouselements of user interface display 1700 (FIG. 17), user interfacedisplay 1800 (FIG. 18), user interface display 1900 (FIG. 19), userinterface display 2000 (FIG. 20), and/or user interface display 2100(FIG. 21). In many embodiments, mobile application 123 (FIG. 1) canprovide an interface for display on mobile device 120 (FIG. 1), whichcan include user interface display 2200. In a number of embodiments, theinterface can display a confirmation to consumer 129 (FIG. 1) thatpayment to merchant 119 (FIG. 1) has successfully completed for thepayment authorized in user interface display 1700 (FIG. 17), userinterface display 1800 (FIG. 18), user interface display 1900 (FIG. 19),and/or user interface display 2000 (FIG. 20).

In a number of embodiments, user interface display 2200 can include atitle bar 2201, a descriptor field 2210, and/or a selection button 2220.In many embodiments, title bar 2201 can include the name of the mobilewallet or mobile application (e.g., mobile application 123 (FIG. 1)).Title bar 2201 can be similar or identical to title bar 1701 (FIG. 17),title bar 1801 (FIG. 18), title bar 1901 (FIG. 19), title bar 2001 (FIG.20), and/or title bar 2101 (FIG. 21).

In many embodiments, descriptor field 2210 can include a message aboutthe success or failure of the payment request, for example, that thepayment is complete. If the request failed, the message can indicatethat the payment failed.

In several embodiments, selection button 2220 can be selected byconsumer 129 (FIG. 1) to dismiss the message displayed in user interfacedisplay 2200.

Turning ahead in the drawings, FIG. 23 illustrates a flow chart for amethod 2300, according to an embodiment. In some embodiments, method2300 can be a method of facilitating secure payment transactions. Method2300 is merely exemplary and is not limited to the embodiments presentedherein. Method 2300 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, the procedures, the processes, and/or the activities ofmethod 2300 can be performed in the order presented. In otherembodiments, the procedures, the processes, and/or the activities ofmethod 2300 can be performed in any suitable order. In still otherembodiments, one or more of the procedures, the processes, and/or theactivities of method 2300 can be combined or skipped. In someembodiments, method 2300 can be performed by mobile device 120 (FIG. 1)and/or mobile application 123 (FIG. 1).

Referring to FIG. 23, method 2300 can include a block 2301 of receivinga preauthorization code at a mobile device while the mobile device is indata communication with a mobile wallet provider. For example, themobile device can be in data communication with the mobile walletprovider, such as through communication channel 171 (FIG. 1). The mobiledevice can be similar or identical to mobile device 120 (FIG. 1). Themobile wallet provider can be similar or identical to mobile walletprovider 160 (FIG. 1). In some embodiments, the preauthorization codecan be similar or identical to the preauthorization code describedabove. In a number of embodiments, the preauthorization code can includea preauthorization amount, an expiration time, and a digital signature.

In several embodiments, the mobile wallet provider can be operated by afirst financial institution that maintains a first account of a user ofthe mobile device. The user of the mobile device can be similar oridentical to consumer 129 (FIG. 1). The first financial institution canbe similar or identical to financial institution 130 (FIG. 1). The firstaccount of the user can be similar or identical to one or more ofconsumer accounts 131 (FIG. 1). In other embodiments, the mobile walletprovider can be operated by an entity that is different from the firstfinancial institution. In several embodiments, the digital signature ofthe preauthorization code can be cryptographically signed by the firstfinancial institution that maintains the first account of the user.

In several embodiments, method 2300 also can include a block 2302 ofstoring the preauthorization code in the mobile device. In manyembodiments, the preauthorization code can be stored in the mobiledevice in an encrypted form.

In a number of embodiments, method 2300 additionally can include a block2303 of receiving, at the mobile device, an authorization from a user ofthe mobile device for a transaction having a transaction amount whilethe user is at a point-of-sale terminal of a first entity. Thepoint-of-sale terminal can be similar or identical to point-of-saleterminal 110 (FIG. 1). The first entity can be similar or identical tomerchant 119 (FIG. 1). The authorization from the user can be similar oridentical to the authorization described above. In many embodiments, thetransaction can be for a purchase by the user of one or more items fromthe first entity.

In several embodiments, method 2300 further can include a block 2304 ofdetermining that the mobile device is unable to communicate with themobile wallet provider. For example, the mobile device can be “offline,”as described above. As an example, the mobile device can be unable tocommunicate with the mobile wallet provider when a connection betweenthe two, such as communication channel 171 (FIG. 1), is down.

In a number of embodiments, method 2300 additionally can include a block2305 of verifying that the transaction amount is less than or equal tothe preauthorization amount.

In several embodiments, method 2300 further can include a block 2306 ofproviding a transaction code from the mobile device to the point-of-saleterminal to cause the first entity to send the transaction amount andthe preauthorization code to a transaction system, and to cause thetransaction system to send an approval for the transaction in real-timewhile the user remains at the point-of-sale terminal of the firstentity. The transaction system can be similar or identical totransaction system 140 (FIG. 1). In many embodiments, block 2306 can beperformed while the mobile device is unable to communicate with themobile wallet provider. The transaction code can be similar or identicalto the transaction code described above. In some embodiments, thetransaction code can include the preauthorization code, a transactionidentifier, and the transaction amount.

In some embodiments, block 2306 of providing a transaction code from themobile device to the point-of-sale terminal to cause the first entity tosend the transaction amount and the preauthorization code to atransaction system, and to cause the transaction system to send anapproval for the transaction in real-time while the user remains at thepoint-of-sale terminal of the first entity can include displaying thetransaction code as a matrix barcode on a screen of the mobile device.In many embodiments, the point-of-sale terminal can scan the matrixbarcode from the screen of the mobile device. In other embodiment, block2306 of providing a transaction code from the mobile device to thepoint-of-sale terminal to cause the first entity to send the transactionamount and the preauthorization code to a transaction system, and tocause the transaction system to send an approval for the transaction inreal-time while the user remains at the point-of-sale terminal of thefirst entity can include transmitting the transaction code from themobile device to the point-of-sale terminal using a proximity-basedwireless data communication protocol.

In some embodiments, the approval can include one of: (a) a settlementcredit push of funds for the transaction amount from the first accountof the user to a second account of the first entity, or (b) anirrevocable promise to pay the transaction amount from the first accountto the second account. The second account can be similar or identical tomerchant account 151 (FIG. 1).

In various embodiments, the transaction amount and the preauthorizationcode can be sent to the transaction system from the first entity througha second financial institution that maintains the second account of thefirst entity, such as through communication channels 173 and 174 (FIG.1). The second financial institution can be similar or identical tofinancial institution 150 (FIG. 1). In other embodiments, thetransaction amount and the preauthorization code can be sent to thetransaction system from the first entity directly, such as communicationchannel 178 (FIG. 1).

Turning ahead in the drawings, FIG. 24 illustrates a flow chart for amethod 2400, according to an embodiment. In some embodiments, method2400 can be a method of facilitating secure payment transactions. Method2400 is merely exemplary and is not limited to the embodiments presentedherein. Method 2400 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, the procedures, the processes, and/or the activities ofmethod 2400 can be performed in the order presented. In otherembodiments, the procedures, the processes, and/or the activities ofmethod 2400 can be performed in any suitable order. In still otherembodiments, one or more of the procedures, the processes, and/or theactivities of method 2400 can be combined or skipped. In someembodiments, method 2400 can be performed by transaction system 140(FIG. 1). In some embodiments, method 2400 and other blocks in method2400 can include using a distributed network including distributedmemory architecture to perform the associated activity. This distributedarchitecture can reduce the impact on the network and system resourcesto reduce congestion in bottlenecks while still allowing data to beaccessible from a central location.

Referring to FIG. 24, method 2400 can include a block 2401 of receivinga transaction amount and a preauthorization code from a first entity.The first entity can be similar or identical to merchant 119 (FIG. 1).In some embodiments, the preauthorization code can be similar oridentical to the preauthorization code described above. In manyembodiments, the preauthorization code can include a preauthorizationamount, an expiration time, and a digital signature. In someembodiments, the transaction amount can be for a transaction authorizedby a user of a mobile device at a point-of-sale terminal of the firstentity. The user of the mobile device can be similar or identical toconsumer 129 (FIG. 1). The mobile device can be similar or identical tomobile device 120 (FIG. 1). The point-of-sale terminal can be similar oridentical to point-of-sale terminal 110 (FIG. 1).

In many embodiments, the transaction amount can be less than or equal tothe preauthorization amount. In some embodiments, the mobile devicereceived the preauthorization code and stored the preauthorization codein the mobile device while the mobile device was in data communicationwith a mobile wallet provider, such as through communication channel 171(FIG. 1). The mobile wallet provider can be similar or identical tomobile wallet provider 160 (FIG. 1). In many embodiments, the mobiledevice provided a transaction code to the point-of-sale terminal whilethe mobile device was unable to communicate with the mobile walletprovider. For example, the mobile device can be “offline,” as describedabove. As an example, the mobile device can be unable to communicatewith the mobile wallet provider when a connection between the two, suchas communication channel 171 (FIG. 1), is down.

In some embodiments, the transaction code can include thepreauthorization code, a transaction identifier for the transaction, andthe transaction amount. In many embodiments, the transaction code can beprovided from the mobile device to the point-of-sale terminal by themobile device displaying the transaction code as a matrix barcode on ascreen of the mobile device, and the point-of-sale terminal scanning thematrix barcode from the screen of the mobile device. In otherembodiments, the transaction code can be provided from the mobile deviceto the point-of-sale terminal by the mobile device transmitting thetransaction code from the mobile device to the point-of-sale terminalusing a proximity-based wireless data communication protocol.

In some embodiments, the digital signature of the preauthorization codecan be cryptographically signed by a first financial institution thatmaintains a first account of the user. The first financial institutioncan be similar or identical to financial institution 130 (FIG. 1). Thefirst account of the user can be similar or identical to one or more ofconsumer accounts 131 (FIG. 1).

In some embodiments, the transaction can be for a purchase by the userof one or more items from the first entity. In many embodiments, themobile wallet provider can be operated by the first financialinstitution that maintains the first account of the user. In otherembodiments, the mobile wallet provider can be operated by an entitythat is different from the first financial institution. In someembodiments, the preauthorization code can be stored in the mobiledevice in an encrypted form.

In several embodiments, method 2400 also can include a block 2402 ofverifying the preauthorization code using the digital signature of thepreauthorization code. In some embodiments, block 2402 of verifying thepreauthorization code using the digital signature of thepreauthorization code can include verifying that the transaction amountis less than or equal to the preauthorization amount, and verifying thatthe expiration time is at a future time (e.g., not yet expired).

In a number of embodiments, method 2400 additionally can include a block2403 of sending an approval for the transaction to the first entity inreal-time while the user remains at the point-of-sale terminal of thefirst entity. In some embodiments, the approval can include one of: (a)a settlement credit push of funds for the transaction amount from thefirst account of the user to a second account of the first entity, or(b) an irrevocable promise to pay the transaction amount from the firstaccount to the second account. The second account can be similar oridentical to merchant account 151 (FIG. 1).

In various embodiments, the transaction amount and the preauthorizationcode can be sent to the transaction system from the first entity througha second financial institution that maintains the second account of thefirst entity, such as through communication channels 173 and 174 (FIG.1). The second financial institution can be similar or identical tofinancial institution 150 (FIG. 1). In other embodiments, thetransaction amount and the preauthorization code can be sent to thetransaction system from the first entity directly, such as communicationchannel 178 (FIG. 1).

Turning ahead in the drawings, FIG. 25 illustrates a flow chart for amethod 2500, according to an embodiment. In some embodiments, method2500 can be a method of facilitating secure payment transactions. Method2500 is merely exemplary and is not limited to the embodiments presentedherein. Method 2500 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, the procedures, the processes, and/or the activities ofmethod 2500 can be performed in the order presented. In otherembodiments, the procedures, the processes, and/or the activities ofmethod 2500 can be performed in any suitable order. In still otherembodiments, one or more of the procedures, the processes, and/or theactivities of method 2500 can be combined or skipped. In someembodiments, method 2500 can be performed by point-of-sale terminal 110(FIG. 1). In some embodiments, method 2500 and other blocks in method2500 can include using a distributed network including distributedmemory architecture to perform the associated activity. This distributedarchitecture can reduce the impact on the network and system resourcesto reduce congestion in bottlenecks while still allowing data to beaccessible from a central location.

Referring to FIG. 25, method 2500 can include a block 2501 of receivinga transaction code from a mobile device at a point-of-sale terminal of afirst entity while the mobile device is unable to communicate with amobile wallet provider. The mobile device can be similar or identical tomobile device 120 (FIG. 1). The point-of-sale terminal can be similar oridentical to point-of-sale terminal 110 (FIG. 1). The first entity canbe similar or identical to merchant 119 (FIG. 1). The mobile walletprovider can be similar or identical to mobile wallet provider 160 (FIG.1). In many embodiments, the transaction code can include apreauthorization code, a transaction identifier for a transactionauthorized by a user of the mobile device at the point-of-sale terminal,and a transaction amount for the transaction. The user of the mobiledevice can be similar or identical to consumer 129 (FIG. 1).

In many embodiments, the mobile device received the preauthorizationcode and stored the preauthorization code in the mobile device while themobile device was in data communication with the mobile wallet provider,such as through communication channel 171 (FIG. 1). In some embodiments,the preauthorization code includes a preauthorization amount, anexpiration time, and a digital signature. In many embodiments, thetransaction amount can be less than or equal to the preauthorizationamount.

In some embodiments, block 2501 of receiving a transaction code from amobile device at a point-of-sale terminal of a first entity while themobile device is unable to communicate with a mobile wallet provider caninclude scanning a matrix barcode displayed on the screen of the mobiledevice. The matrix barcode can include the transaction code. In otherembodiments, block 2501 of receiving a transaction code from a mobiledevice at a point-of-sale terminal of a first entity while the mobiledevice is unable to communicate with a mobile wallet provider caninclude receiving a transmission of the transaction code from the mobiledevice using a proximity-based wireless data communication protocol.

In many embodiments, the digital signature of the preauthorization codecan be cryptographically signed by a first financial institution thatmaintains a first account of the user. The first financial institutioncan be similar or identical to financial institution 130 (FIG. 1). Thefirst account of the user can be similar or identical to one or more ofconsumer accounts 131 (FIG. 1). In some embodiments, the transaction canbe for a purchase by the user of one or more items from the firstentity. In many embodiments, the mobile wallet provider can be operatedby the first financial institution that maintains the first account ofthe user. In other embodiments, the mobile wallet provider can beoperated by an entity that is different from the first financialinstitution. In some embodiments, the preauthorization code can bestored in the mobile device in an encrypted form.

In several embodiments, method 2500 also can include a block 2502 ofsending the transaction amount and the preauthorization code to atransaction system. The transaction system can be similar or identicalto transaction system 140 (FIG. 1). In many embodiments, the transactionsystem can verify the preauthorization code using the digital signatureof the preauthorization code before sending the approval for thetransaction.

In various embodiments, the transaction amount and the preauthorizationcode can be sent to the transaction system from the first entity througha second financial institution that maintains a second account of thefirst entity, such as through communication channels 173 and 174 (FIG.1). The second financial institution can be similar or identical tofinancial institution 150 (FIG. 1). The second account can be similar oridentical to merchant account 151 (FIG. 1). In other embodiments, thetransaction amount and the preauthorization code can be sent to thetransaction system from the first entity directly, such as communicationchannel 178 (FIG. 1).

In a number of embodiments, method 2500 additionally can include a block2503 of receiving an approval for the transaction from the transactionsystem in real-time while the user remains at the point-of-saleterminal. In a number of embodiments, the approval can include one of:(a) a settlement credit push of funds for the transaction amount fromthe first account of the user to the second account of the first entity,or (b) an irrevocable promise to pay the transaction amount from thefirst account to the second account.

Turning ahead in the drawings, FIG. 26 illustrates a flow chart for amethod 2600, according to an embodiment. In some embodiments, method2600 can be a method of facilitating secure payment transactions. Method2600 is merely exemplary and is not limited to the embodiments presentedherein. Method 2600 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, the procedures, the processes, and/or the activities ofmethod 2600 can be performed in the order presented. In otherembodiments, the procedures, the processes, and/or the activities ofmethod 2600 can be performed in any suitable order. In still otherembodiments, one or more of the procedures, the processes, and/or theactivities of method 2600 can be combined or skipped. In someembodiments, method 2600 can be performed by mobile device 120 (FIG. 1)and/or mobile application 126 (FIG. 1).

Referring to FIG. 26, method 2600 can include a block 2601 of receiving,at a mobile device from a point-of-sale terminal of a first entity, anidentifier of the first entity, a transaction amount for a transaction,and a transaction identifier for the transaction. The mobile device canbe similar or identical to mobile device 120 (FIG. 1). The point-of-saleterminal can be similar or identical to point-of-sale terminal 110 (FIG.1). The first entity can be similar or identical to merchant 119 (FIG.1). In some embodiments, the identifier of the first entity, thetransaction amount, and the transaction identifier can be received fromthe point-of-sale terminal as part of a digitally signed transactioncode. In several embodiments, the digitally signed transaction code canbe cryptographically signed by the point-of-sale terminal, and/or thedigitally signed transaction code can be verified by the mobile device.

In many embodiments, the transaction can be for a purchase by a user ofone or more items from the first entity. The user of the mobile devicecan be similar or identical to consumer 129 (FIG. 1). In someembodiments, first information about the one or more items can bescanned into the mobile application by the user in a store of the firstentity. In various embodiments, the first information about the one ormore items can be provided by the mobile device to the point-of-saleterminal to cause the point-of-sale terminal to generate the transactionamount for the transaction.

In several embodiments, method 2600 also can include a block 2602 ofreceiving an authorization from the user of the mobile device for thetransaction while the user is at the point-of-sale terminal. In manyembodiments, the mobile device can run a mobile application that isassociated with a mobile wallet provider. The mobile application can besimilar or identical to mobile application 123 (FIG. 1). The mobilewallet provider can be similar or identical to mobile wallet provider160 (FIG. 1). In several embodiments, the mobile wallet provider can beoperated by a first financial institution. The first financialinstitution can be similar or identical to financial institution 130(FIG. 1). In other embodiments, the mobile wallet provider can beoperated by an entity that is different from the first financialinstitution.

In a number of embodiments, method 2600 additionally can include a block2603 of determining that the mobile device is unable to communicate withthe mobile wallet provider. For example, the mobile device can be“offline,” as described above. As an example, the mobile device can beunable to communicate with the mobile wallet provider when a connectionbetween the two, such as communication channel 171 (FIG. 1), is down.

In several embodiments, method 2600 further can include a block 2604 ofgenerating an encrypted transaction code. In many embodiments, theencrypted transaction code can include a preauthorization from the userto pay the first entity for the transaction amount from a first accountof the user maintained by the first financial institution. The firstaccount of the user can be similar or identical to one or more ofconsumer accounts 131 (FIG. 1). In some embodiments, thepreauthorization from the user can be digitally signed by the mobiledevice, such that the encrypted transaction code includes a digitalsignature. In many embodiments, the encrypted transaction code can beencrypted by the mobile device using a public key of the mobile walletprovider.

In a number of embodiments, method 2600 additionally can include a block2605 of sending the encrypted transaction code from the mobile device tothe point-of-sale terminal to cause the encrypted transaction code to besent through a proxy communication channel extending from thepoint-of-sale terminal, through a transaction system, to the mobilewallet provider, to cause the mobile wallet provider to decrypt theencrypted transaction code and verify the preauthorization from theuser, to cause the first financial institution to retrieve from thetransaction system an account identifier of a second account of thefirst entity maintained by a second financial institution based on theidentifier of the first entity and send to the transaction systempayment information regarding a payment to be made to the second accountfrom the first account for the transaction, to cause the paymentinformation to be routed through the transaction system to the secondfinancial institution, and to cause the point-of-sale terminal toreceive a notification of the payment for the transaction in real-timewhile the user remains at the point-of-sale terminal. The transactionsystem can be similar or identical to transaction system 140 (FIG. 1).The second account can be similar or identical to merchant account 151(FIG. 1). The second financial institution can be similar or identicalto financial institution 150 (FIG. 1). The proxy communication channelcan be similar or identical to various embodiments of the proxycommunication channel described above. For example, in some embodiments,the proxy communication channel from the point-of-sale terminal to themobile wallet provider can extend through the second financialinstitution between the point-of-sale terminal and the transactionsystem. In other embodiments, the proxy communication channel from thepoint-of-sale terminal to the mobile wallet provider can extend betweenthe point-of-sale terminal and the transaction system without includingthe transaction system. In many embodiments, the transaction system canbe maintained by an entity that is different from the first entity, thefirst financial institution, and the second financial institution.

In some embodiments, the mobile wallet provider can verify thepreauthorization from the user using the digital signature. In variousembodiments, the encrypted transaction code can be decrypted by themobile wallet provider using a private key of the mobile walletprovider. In a number of embodiments, block 2605 can include displayingthe encrypted transaction code as a matrix barcode on a screen of themobile device. The point-of-sale terminal can scan the matrix barcodefrom the screen of the mobile device. In other embodiments, block 2605can include transmitting the encrypted transaction code from the mobiledevice to the point-of-sale terminal using a proximity-based wirelessdata communication protocol.

In many embodiments, the payment information can include the transactionidentifier, the account identifier of the second account, thetransaction amount, and/or one of: (a) a settlement credit push of fundsfor the transaction amount from the first account of the user to thesecond account of the first entity, or (b) an irrevocable promise to paythe transaction amount from the first account to the second account.

Turning ahead in the drawings, FIG. 27 illustrates a flow chart for amethod 2700, according to an embodiment. In some embodiments, method2700 can be a method of facilitating secure payment transactions. Method2700 is merely exemplary and is not limited to the embodiments presentedherein. Method 2700 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, the procedures, the processes, and/or the activities ofmethod 2700 can be performed in the order presented. In otherembodiments, the procedures, the processes, and/or the activities ofmethod 2700 can be performed in any suitable order. In still otherembodiments, one or more of the procedures, the processes, and/or theactivities of method 2700 can be combined or skipped. In someembodiments, method 2700 can be performed by transaction system 140(FIG. 1). In some embodiments, method 2700 and other blocks in method2700 can include using a distributed network including distributedmemory architecture to perform the associated activity. This distributedarchitecture can reduce the impact on the network and system resourcesto reduce congestion in bottlenecks while still allowing data to beaccessible from a central location.

Referring to FIG. 27, method 2700 can include a block 2701 of receiving,at a transaction system being situated along a proxy communicationchannel extending from a point-of-sale terminal of a first entity to amobile wallet provider, an encrypted transaction code. The transactionsystem can be similar or identical to transaction system 140 (FIG. 1).The point-of-sale terminal can be similar or identical to point-of-saleterminal 110 (FIG. 1). The first entity can be similar or identical tomerchant 119 (FIG. 1). The mobile wallet provider can be similar oridentical to mobile wallet provider 160 (FIG. 1).

In many embodiments, the encrypted transaction code can be generated andsent to the point-of-sale terminal by a mobile device that runs a mobileapplication associated with the mobile wallet provider. The mobiledevice can be similar or identical to mobile device 120 (FIG. 1). Themobile application can be similar or identical to mobile application 123(FIG. 1). In some embodiments, the mobile device can receive from apoint-of-sale terminal an identifier of the first entity, a transactionamount of a transaction, and a transaction identifier for thetransaction. The point-of-sale terminal can be similar or identical topoint-of-sale terminal 110 (FIG. 1). In various embodiments, the mobiledevice can receives an authorization from a user of the mobile devicefor the transaction while the user is at the point-of-sale terminal. Theuser of the mobile device can be similar or identical to consumer 129(FIG. 1). In some embodiments, the mobile device can determine that themobile device is unable to communicate with the mobile wallet provider.For example, the mobile device can be “offline,” as described above. Asan example, the mobile device can be unable to communicate with themobile wallet provider when a connection between the two, such ascommunication channel 171 (FIG. 1), is down.

In many embodiments, the encrypted transaction code can include apreauthorization from the user to pay the first entity for thetransaction amount from a first account of the user maintained by afirst financial institution. The first financial institution can besimilar or identical to financial institution 130 (FIG. 1). The firstaccount of the user can be similar or identical to one or more ofconsumer accounts 131 (FIG. 1).

The proxy communication channel can be similar or identical to variousembodiments of the proxy communication channel described above. Forexample, in some embodiments, the proxy communication channel from thepoint-of-sale terminal to the mobile wallet provider can extend througha second financial institution between the point-of-sale terminal andthe transaction system. The second financial institution can be similaror identical to financial institution 150 (FIG. 1). In otherembodiments, the proxy communication channel from the point-of-saleterminal to the mobile wallet provider can extend between thepoint-of-sale terminal and the transaction system without including thetransaction system.

In some embodiments, the transaction system can be maintained by anentity that is different from the first entity, the first financialinstitution, and the second financial institution. In variousembodiments, the mobile wallet provider can be operated by the firstfinancial institution. In many embodiments, the identifier of the firstentity, the transaction amount, and the transaction identifier can besent from the point-of-sale terminal to the mobile device as part of adigitally signed transaction code.

In many embodiments, the digitally signed transaction code can becryptographically signed by the point-of-sale terminal, and/or thedigitally signed transaction code can be verified by the mobile device.In some embodiments, the preauthorization from the user can be digitallysigned by the mobile device, such that the encrypted transaction codeincludes a digital signature. In several embodiments, the encryptedtransaction code can be encrypted by the mobile device using a publickey of the mobile wallet provider.

In some embodiments, the transaction can be for a purchase by the userof one or more items from the first entity. In many embodiments, firstinformation about the one or more items can be scanned into the mobileapplication by the user in a store of the first entity. In variousembodiments, the first information about the one or more items can bereceived at the point-of-sale terminal from the mobile device to causethe point-of-sale terminal to generate the transaction amount for thetransaction.

In many embodiments, the point-of-sale terminal can receive theencrypted transaction code by scanning the encrypted transaction code asa matrix barcode from a screen of the mobile device. In otherembodiments, the point-of-sale terminal can receive the encryptedtransaction from the mobile device using a proximity-based wireless datacommunication protocol.

In several embodiments, method 2700 also can include a block 2702 ofsending the encrypted transaction code through the proxy communicationchannel to the mobile wallet provider, to cause the mobile walletprovider to decrypt the encrypted transaction code and verify thepreauthorization from the user. In many embodiments, the mobile walletprovider can verify the preauthorization from the user using the digitalsignature. In some embodiments, the encrypted transaction code can bedecrypted by the mobile wallet provider using a private key of themobile wallet provider.

In a number of embodiments, method 2700 additionally can include a block2703 of receiving, from the first financial institution, a requestincluding the identifier of the first entity.

In several embodiments, method 2700 also can include a block 2704 ofdetermining an account identifier of a second account of the firstentity maintained by the second financial institution based on theidentifier of the first entity. The second account can be similar oridentical to merchant account 151 (FIG. 1). For example, the accountidentified of the second account can be determined using merchantaccount database 141 (FIG. 1) and/or the identifier of the first entity.

In a number of embodiments, method 2700 additionally can include a block2705 of sending the account identifier of the second account to thefirst financial institution.

In several embodiments, method 2700 also can include a block 2706 ofreceiving, from the first financial institution, payment informationregarding a payment to be made to the second account from the firstaccount for the transaction. In some embodiments, the paymentinformation can include the transaction identifier, the accountidentifier of the second account, the transaction amount, and/or one of:(a) a settlement credit push of funds for the transaction amount fromthe first account of the user to the second account of the first entity,or (b) an irrevocable promise to pay the transaction amount from thefirst account to the second account.

In a number of embodiments, method 2700 additionally can include a block2707 of sending the payment information to the second financialinstitution, to cause the point-of-sale terminal to receive anotification in real-time while the user remains at the point-of-saleterminal.

Turning ahead in the drawings, FIG. 28 illustrates a flow chart for amethod 2800, according to an embodiment. In some embodiments, method2800 can be a method of facilitating secure payment transactions. Method2800 is merely exemplary and is not limited to the embodiments presentedherein. Method 2800 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, the procedures, the processes, and/or the activities ofmethod 2800 can be performed in the order presented. In otherembodiments, the procedures, the processes, and/or the activities ofmethod 2800 can be performed in any suitable order. In still otherembodiments, one or more of the procedures, the processes, and/or theactivities of method 2800 can be combined or skipped. In someembodiments, method 2800 can be performed by point-of-sale terminal 110(FIG. 1). In some embodiments, method 2800 and other blocks in method2800 can include using a distributed network including distributedmemory architecture to perform the associated activity. This distributedarchitecture can reduce the impact on the network and system resourcesto reduce congestion in bottlenecks while still allowing data to beaccessible from a central location.

Referring to FIG. 28, method 2800 can include a block 2801 of sending,to a mobile device from a point-of-sale terminal of a first entity, anidentifier of the first entity, a transaction amount of a transaction,and a transaction identifier for the transaction. The mobile device canbe similar or identical to mobile device 120 (FIG. 1). The point-of-saleterminal can be similar or identical to point-of-sale terminal 110 (FIG.1). The first entity can be similar or identical to merchant 119 (FIG.1).

In many embodiments, the mobile device can run a mobile application thatis associated with a mobile wallet provider. The mobile application canbe similar or identical to mobile application 123 (FIG. 1). The mobilewallet provider can be similar or identical to mobile wallet provider160 (FIG. 1). In several embodiments, the mobile device can receive anauthorization from a user of the mobile device for the transaction whilethe user is at the point-of-sale terminal. The user of the mobile devicecan be similar or identical to consumer 129 (FIG. 1). In someembodiments, the mobile device can determines that the mobile device isunable to communicate with the mobile wallet provider. For example, themobile device can be “offline,” as described above. As an example, themobile device can be unable to communicate with the mobile walletprovider when a connection between the two, such as communicationchannel 171 (FIG. 1), is down. In many embodiments, the mobile devicecan generates an encrypted transaction code. In some embodiments, theencrypted transaction code can include a preauthorization from the userto pay the first entity for the transaction amount from a first accountof the user maintained by a first financial institution. The firstfinancial institution can be similar or identical to financialinstitution 130 (FIG. 1). The first account of the user can be similaror identical to one or more of consumer accounts 131 (FIG. 1).

In some embodiments, the mobile wallet provider can be operated by thefirst financial institution. In various embodiments, the identifier ofthe first entity, the transaction amount, and the transaction identifiercan be sent from the point-of-sale terminal to the mobile device as partof a digitally signed transaction code. In many embodiments, thedigitally signed transaction code can be cryptographically signed by thepoint-of-sale terminal. In a number of embodiments, the digitally signedtransaction code can be verified by the mobile device. In someembodiments, the identifier of the first entity, the transaction amount,and the transaction identifier can be sent from the point-of-saleterminal to the mobile device as part of a digitally signed transactioncode. In several embodiments, the digitally signed transaction code canbe cryptographically signed by the point-of-sale terminal. In manyembodiments, the digitally signed transaction code can be verified bythe mobile device. In some embodiments, the encrypted transaction codecan be encrypted by the mobile device using a public key of the mobilewallet provider. In several embodiments, the encrypted transaction codecan be decrypted by the mobile wallet provider using a private key ofthe mobile wallet provider.

In a number of embodiments, the transaction can be for a purchase by theuser of one or more items from the first entity. In some embodiments,first information about the one or more items can be scanned into themobile application by the user in a store of the first entity. Invarious embodiments, the first information about the one or more itemscan be received at the point-of-sale terminal from the mobile device tocause the point-of-sale terminal to generate the transaction amount forthe transaction.

In several embodiments, method 2800 also can include a block 2802 ofreceiving the encrypted transaction code from the mobile device. In someembodiments, block 2802 of receiving the encrypted transaction code fromthe mobile device can include scanning the encrypted transaction code asa matrix barcode from a screen of the mobile device. In otherembodiments, block 2802 of receiving the encrypted transaction code fromthe mobile device can include receiving the encrypted transaction codefrom the mobile device using a proximity-based wireless datacommunication protocol.

In a number of embodiments, method 2800 additionally can include a block2803 of sending the encrypted transaction code through a proxycommunication channel extending from the point-of-sale terminal, througha transaction system, to the mobile wallet provider, to cause the mobilewallet provider to decrypt the encrypted transaction code and verify thepreauthorization from the user, to cause the first financial institutionto retrieve from the transaction system an account identifier of asecond account of the first entity maintained by a second financialinstitution based on the identifier of the first entity and send to thetransaction system payment information regarding a payment to be made tothe second account from the first account for the transaction, and tocause the payment information to be routed through the transactionsystem to the second financial institution. The second financialinstitution can be similar or identical to financial institution 150(FIG. 1). The second account can be similar or identical to merchantaccount 151 (FIG. 1). The transaction system can be similar or identicalto transaction system 140 (FIG. 1). In several embodiments, thetransaction system can be maintained by an entity that is different fromthe first entity, the first financial institution, and the secondfinancial institution.

In many embodiments, the proxy communication channel can be similar oridentical to various embodiments of the proxy communication channeldescribed above. For example, in some embodiments, the proxycommunication channel from the point-of-sale terminal to the mobilewallet provider can extend through the second financial institutionbetween the point-of-sale terminal and the transaction system. In otherembodiments, the proxy communication channel from the point-of-saleterminal to the mobile wallet provider can extend between thepoint-of-sale terminal and the transaction system without including thetransaction system.

In several embodiments, the payment information can include thetransaction identifier, the account identifier of the second account,the transaction amount, and/or one of: (a) a settlement credit push offunds for the transaction amount from the first account of the user tothe second account of the first entity, or (b) an irrevocable promise topay the transaction amount from the first account to the second account.

In several embodiments, method 2800 also can include a block 2804 ofreceiving, at the point-of-sale terminal, a notification of the paymentfor the transaction in real-time while the user remains at thepoint-of-sale terminal.

Returning again to FIG. 1, as described above, point-of-sale terminal110 can include one or more systems, such as checkout system 111,communication system 112, payment system 113, consumer informationsystem 114, security system 115, preauthorization system 116, and/orproxy communication system 117. Point-of-sale terminal 110 and thesystems therein are merely exemplary and are not limited to theembodiments presented herein. Point-of-sale terminal 110 can be employedin many different embodiments or examples not specifically depicted ordescribed herein. In some embodiments, certain elements, systems, ormodules of point-of-sale terminal 110 can perform various procedures,processes, and/or acts. In other embodiments, the procedures, processes,and/or acts can be performed by other suitable elements, systems, ormodules.

In many embodiments, checkout system 111 can at least partially performblock 501 (FIG. 5) of determining, at a point-of-sale terminal at astore of a merchant, a payment amount for one or more items to bepurchased from the merchant by a consumer, block 901 (FIG. 9) ofdetermining, at a point-of-sale terminal at a store of a merchant, apayment amount for one or more items to be purchased from the merchantby a consumer in a transaction, and/or block 1601 (FIG. 16) ofdetermining, at a point-of-sale terminal at a store of a merchant, apayment amount for one or more items to be purchased from the merchantby a consumer in a transaction.

In several embodiments, communication system 112 can at least partiallyperform block 502 (FIG. 5) of sending first information from thepoint-of-sale terminal to a mobile device used by the consumer, block503 (FIG. 5) of receiving at the point-of-sale terminal from the mobiledevice, information about the consumer, block 504 (FIG. 5) of receiving,at the point-of-sale terminal from the second financial institution, anotification to satisfy an expectation of the merchant for payment fromthe consumer, block 903 (FIG. 9) of providing the transaction code to amobile device being used by the consumer, block 904 (FIG. 9) ofreceiving, at the point-of-sale terminal, a notification of payment forthe transaction in real-time while the consumer remains at the store ofthe merchant, block 1602 (FIG. 16) of sending first information from thepoint-of-sale terminal to a mobile device used by the consumer, block1603 (FIG. 16) of receiving, at the point-of-sale terminal, anotification of payment for the transaction in real-time while theconsumer remains at the store of the merchant, block 2501 (FIG. 25) ofreceiving a transaction code from a mobile device at a point-of-saleterminal of a first entity while the mobile device is unable tocommunicate with a mobile wallet provider, block 2502 (FIG. 25) ofsending the transaction amount and the preauthorization code to atransaction system, and/or block 2801 (FIG. 28) of sending, to a mobiledevice from a point-of-sale terminal of a first entity, an identifier ofthe first entity, a transaction amount of a transaction, and atransaction identifier for the transaction.

In a number of embodiments, payment system 113 can at least partiallyperform block 504 (FIG. 5) of receiving, at the point-of-sale terminalfrom the second financial institution, a notification to satisfy anexpectation of the merchant for payment from the consumer, block 904(FIG. 9) of receiving, at the point-of-sale terminal, a notification ofpayment for the transaction in real-time while the consumer remains atthe store of the merchant, block 2503 (FIG. 25) of receiving an approvalfor the transaction from the transaction system in real-time while theuser remains at the point-of-sale terminal, and/or block 2804 (FIG. 28)of receiving, at the point-of-sale terminal, a notification of thepayment for the transaction in real-time while the user remains at thepoint-of-sale terminal.

In various embodiments, consumer information system 114 can at leastpartially perform block 503 (FIG. 5) of receiving at the point-of-saleterminal from the mobile device, information about the consumer.

In a number of embodiments, security system 115 can at least partiallyperform block 902 (FIG. 9) of generating a transaction code including amerchant public identifier, the payment amount, a transaction identifierfor the transaction, and a digital signature, and/or block 2801 (FIG.28) of sending, to a mobile device from a point-of-sale terminal of afirst entity, an identifier of the first entity, a transaction amount ofa transaction, and a transaction identifier for the transaction.

In a number of embodiments, preauthorization system 116 can at leastpartially perform block 2501 (FIG. 25) of receiving a transaction codefrom a mobile device at a point-of-sale terminal of a first entity whilethe mobile device is unable to communicate with a mobile walletprovider, and/or block 2502 (FIG. 25) of sending the transaction amountand the preauthorization code to a transaction system.

In many embodiments, proxy communication system 117 can at leastpartially perform block 2802 (FIG. 28) of receiving the encryptedtransaction code from the mobile device, and/or block 2803 (FIG. 28) ofsending the encrypted transaction code through a proxy communicationchannel extending from the point-of-sale terminal, through a transactionsystem, to the mobile wallet provider, to cause the mobile walletprovider to decrypt the encrypted transaction code and verify thepreauthorization from the user, to cause the first financial institutionto retrieve from the transaction system an account identifier of asecond account of the first entity maintained by a second financialinstitution based on the identifier of the first entity and send to thetransaction system payment information regarding a payment to be made tothe second account from the first account for the transaction, and tocause the payment information to be routed through the transactionsystem to the second financial institution

Continuing with FIG. 1, as described above, mobile device 120 caninclude one or more systems, such as authentication system 121, accountsystem 122, communication system 124, security system 125, loan system126, stand-in credit system 127, and/or proxy communication system 128.Mobile device 120 and the systems therein are merely exemplary and arenot limited to the embodiments presented herein. Mobile device 120 canbe employed in many different embodiments or examples not specificallydepicted or described herein. In some embodiments, certain elements,systems, or modules of mobile device 120 can perform various procedures,processes, and/or acts. In other embodiments, the procedures, processes,and/or acts can be performed by other suitable elements, systems, ormodules.

In many embodiments, authentication system 121 can at least partiallyperform block 401 (FIG. 4) of performing, at a mobile device, apreliminary identity authentication of a consumer using the mobiledevice, block 407 (FIG. 4) of performing, at the mobile device, theadditional identity authentication of the consumer using the mobiledevice, and/or block 1301 (FIG. 13) of performing, at a mobile devicebeing used by a consumer, an identity authentication of the consumer.

In several embodiments, account system 122 can at least partiallyperform block 403 (FIG. 4) of sending, from the mobile device to thefirst financial institution, a preliminary request for accountinformation, block 404 (FIG. 4) of receiving, at the mobile device fromthe first financial institution the account information, block 1304(FIG. 13) of receiving, from the first financial institution, an accountbalance of a demand deposit account of the consumer maintained by thefirst financial institution, and/or block 2303 (FIG. 23) of receiving,at the mobile device, an authorization from a user of the mobile devicefor a transaction having a transaction amount while the user is at apoint-of-sale terminal of a first entity.

In a number of embodiments, communication system 124 can at leastpartially perform block 402 (FIG. 4) of receiving at the mobile devicefirst information from a point-of-sale terminal, block 403 (FIG. 4) ofsending, from the mobile device to the first financial institution, apreliminary request for account information, block 404 (FIG. 4) ofreceiving, at the mobile device from the first financial institution,the account information, block 405 (FIG. 4) of sending, from the mobiledevice to the first financial institution, a first request to pay themerchant for the payment amount from the first account for one or moreitems to be purchased from the merchant by the consumer, block 406 (FIG.4) of receiving, at the mobile device from the first financialinstitution, an additional authentication request to perform anadditional identity authentication of the consumer using the mobiledevice, block 408 (FIG. 4) of sending, from the mobile device to thefirst financial institution, a response to the additional authenticationrequest, block 1001 (FIG. 10) of receiving, at a mobile device beingused by a consumer, a transaction code from a point-of-sale terminal ata store of a merchant, block 1003 (FIG. 10) of receiving from theconsumer an approval for the transaction, block 1004 (FIG. 10) ofsending, from the mobile device, a request to pay the merchant for thepayment amount from a first account of the consumer maintained by afirst financial institution, block 1302 (FIG. 13) of receiving, at themobile device, first information from a point-of-sale terminal at astore of a merchant, block 1303 (FIG. 13) of sending, from the mobiledevice, a request to pay the merchant for the payment amount from one ormore first accounts of the consumer maintained by a first financialinstitution, block 1305 (FIG. 13) of displaying the account balance ofthe demand deposit account to the consumer, block 2301 (FIG. 23) ofreceiving a preauthorization code at a mobile device while the mobiledevice is in data communication with a mobile wallet provider, block2304 (FIG. 23) of determining that the mobile device is unable tocommunicate with the mobile wallet provider, block 2306 (FIG. 23) ofproviding a transaction code from the mobile device to the point-of-saleterminal to cause the first entity to send the transaction amount andthe preauthorization code to a transaction system, and to cause thetransaction system to send an approval for the transaction in real-timewhile the user remains at the point-of-sale terminal of the firstentity, block 2601 (FIG. 26) of receiving, at a mobile device from apoint-of-sale terminal of a first entity, an identifier of the firstentity, a transaction amount for a transaction, and a transactionidentifier for the transaction, block 2602 (FIG. 26) of receiving anauthorization from the user of the mobile device for the transactionwhile the user is at the point-of-sale terminal, block 2603 (FIG. 26) ofdetermining that the mobile device is unable to communicate with themobile wallet provider, and/or block 2605 (FIG. 26) of sending theencrypted transaction code from the mobile device to the point-of-saleterminal to cause the encrypted transaction code to be sent through aproxy communication channel extending from the point-of-sale terminal,through a transaction system, to the mobile wallet provider, to causethe mobile wallet provider to decrypt the encrypted transaction code andverify the preauthorization from the user, to cause the first financialinstitution to retrieve from the transaction system an accountidentifier of a second account of the first entity maintained by asecond financial institution based on the identifier of the first entityand send to the transaction system payment information regarding apayment to be made to the second account from the first account for thetransaction, to cause the payment information to be routed through thetransaction system to the second financial institution, and to cause thepoint-of-sale terminal to receive a notification of the payment for thetransaction in real-time while the user remains at the point-of-saleterminal.

In several embodiments, security system 125 can at least partiallyperform block 1002 (FIG. 10) of verifying the digital signature for thetransaction code.

In a number of embodiments, loan system 126 can at least partiallyperform block 1305 (FIG. 13) of displaying the account balance of thedemand deposit account to the consumer, block 1307 (FIG. 13) ofpresenting to the consumer an option to at least partially fund thetransaction using the at least one non-demand deposit account, and/orblock 1308 (FIG. 13) of receiving from the consumer a selection to atleast partially fund the payment amount of the transaction using the atleast one non-demand deposit account.

In a number of embodiments, stand-in credit system 127 can at leastpartially perform block 2301 (FIG. 23) of receiving a preauthorizationcode at a mobile device while the mobile device is in data communicationwith a mobile wallet provider, block 2302 (FIG. 23) of storing thepreauthorization code in the mobile device, and/or block 2305 (FIG. 23)of verifying that the transaction amount is less than or equal to thepreauthorization amount.

In many embodiments, proxy communication system 128 can at leastpartially perform block 2604 (FIG. 26) of generating an encryptedtransaction code.

Continuing with FIG. 1, as described above, financial institution 130can include one or more systems, such as communication system 132,authorization system 133, account system 134, loan system 135,preauthorization system 136, and/or proxy communication system 137.Financial institution 130 and the systems therein are merely exemplaryand are not limited to the embodiments presented herein. Financialinstitution 130 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, certain elements, systems, or modules of financialinstitution 130 can perform various procedures, processes, and/or acts.In other embodiments, the procedures, processes, and/or acts can beperformed by other suitable elements, systems, or modules.

In many embodiments, communication system 132 can at least partiallyperform block 201 (FIG. 2) of receiving, at a first financialinstitution from a mobile device, a preliminary request for accountinformation, block 202 (FIG. 2) of sending, from the first financialinstitution to the mobile device, the account information, block 203(FIG. 2) of receiving, at a first financial institution from a mobiledevice of a consumer, a first request to pay a merchant for a paymentamount from a first account of the consumer maintained by the firstfinancial institution, block 206 (FIG. 2) of sending, from the firstfinancial institution to the first system, a second request to determinethe second information, block 207 (FIG. 2) of receiving, at the firstfinancial institution from the first system, the third information,block 212 (FIG. 2) of sending, from the first financial institution tothe first system, payment information regarding a payment to be made tothe second account from the first account, block 1101 (FIG. 11) ofreceiving, at a first financial institution from a mobile device beingused by a consumer, a request to pay a merchant for a payment amountfrom a first account of the consumer maintained by the first financialinstitution, block 1102 (FIG. 11) of retrieving, at the first financialinstitution from a transaction system, an account identifier for asecond account of the merchant maintained by a second financialinstitution based on the merchant public identifier, block 1103 (FIG.11) of sending, from the first financial institution to the transactionsystem, payment information regarding a payment to be made to the secondaccount from the first account, block 1401 (FIG. 14) of receiving, at afirst financial institution from a mobile device being used by aconsumer, a request to pay a merchant for a payment amount from one ormore first accounts of the consumer maintained by the first financialinstitution, block 1402 (FIG. 14) of retrieving, at the first financialinstitution from a transaction system, an account identifier for asecond account of the merchant maintained by a second financialinstitution based on the merchant identifier, block 1403 (FIG. 14) ofsending, from the first financial institution to the transaction system,payment information regarding a payment to be made to the second accountfrom the one or more first accounts, block 1404 (FIG. 14) of sending, tothe mobile device, an account balance of a demand deposit account of theconsumer maintained by the first financial institution, block 1406 (FIG.14) of sending, to the mobile device, an option to at least partiallyfund the transaction using the at least one non-demand deposit account,and/or block 1407 (FIG. 14) of receiving, from the mobile device, aselection to at least partially fund the payment amount of thetransaction using the at least one non-demand deposit account.

In some embodiments, authorization system 133 can at least partiallyperform block 208 (FIG. 2) of authorizing, at the first financialinstitution, a payment from the first account to the second account,and/or block 209 (FIG. 2) of authenticating an identity of the consumerthat used the mobile device to send the first request to pay themerchant from the first account.

In a number of embodiments, account system 134 can at least partiallyperform block 201 (FIG. 2) of receiving, at a first financialinstitution from a mobile device, a preliminary request for accountinformation, block 202 (FIG. 2) of sending, from the first financialinstitution to the mobile device, the account information, block 204(FIG. 2) of determining, at the first financial institution, secondinformation, block 205 (FIG. 2) of determining, at the first financialinstitution, the second information at least partially based on themerchant identifier and the third information, block 209 (FIG. 2) ofauthenticating an identity of the consumer that used the mobile deviceto send the first request to pay the merchant from the first account,block 210 (FIG. 2) of determining a current status of the first account,block 211 (FIG. 2) of determining available funds of the first account,block 1102 (FIG. 11) of retrieving, at the first financial institutionfrom a transaction system, an account identifier for a second account ofthe merchant maintained by a second financial institution based on themerchant public identifier, block 1402 (FIG. 14) of retrieving, at thefirst financial institution from a transaction system, an accountidentifier for a second account of the merchant maintained by a secondfinancial institution based on the merchant identifier, and/or block1404 (FIG. 14) of sending, to the mobile device, an account balance of ademand deposit account of the consumer maintained by the first financialinstitution.

In some embodiments, loan system 135 can at least partially performblock 1405

(FIG. 14) of determining that the account balance of the demand depositaccount is less than the payment amount of the transaction, block 1406(FIG. 14) of sending, to the mobile device, an option to at leastpartially fund the transaction using the at least one non-demand depositaccount, block 1407 (FIG. 14) of receiving, from the mobile device, aselection to at least partially fund the payment amount of thetransaction using the at least one non-demand deposit account, and/orcreating the loan account.

In a number of embodiments, preauthorization system 136 can at leastpartially perform generating the preauthorization code.

In many embodiments, proxy communication system 137 can at leastpartially perform transmitting the encrypted transaction code along theproxy communication channel.

Continuing with FIG. 1, as described above, transaction system 140 caninclude one or more systems, such as communication system 143, accountsystem 144, transaction system 145, security system 146,preauthorization system 147, and/or proxy communication system 148.Transaction system 140 and the systems therein are merely exemplary andare not limited to the embodiments presented herein. Transaction system140 can be employed in many different embodiments or examples notspecifically depicted or described herein. In some embodiments, certainelements, systems, or modules of transaction system 140 can performvarious procedures, processes, and/or acts. In other embodiments, theprocedures, processes, and/or acts can be performed by other suitableelements, systems, or modules.

In many embodiments, communication system 143 can at least partiallyperform block 301 (FIG. 3) of receiving, at a first system from a firstfinancial institution, a request, block 303 (FIG. 3) of sending thefirst information from the first system to the first financialinstitution, block 304 (FIG. 3) of receiving, at the first system fromthe first financial institution, payment information regarding a paymentto be made to the second account from the first account to pay themerchant for one or more items to be purchased from the merchant by theconsumer for the payment amount, block 306 (FIG. 3) of sending, from thefirst system to the second financial institution, the paymentinformation such that the second financial institution, upon receivingthe payment information, notifies the merchant to satisfy an expectationof the merchant for payment from the consumer, block 1201 (FIG. 12) ofreceiving, at a transaction system from a first entity, a requestincluding a merchant public identifier associated with a merchant, block1203 (FIG. 12) of sending the account identifier to the first financialinstitution, block 1204 (FIG. 12) of receiving, at the transactionsystem from the first financial institution, payment informationregarding a payment to be made to the second account from the firstaccount, block 1205 (FIG. 12) of sending, from the transaction system tothe second financial institution, the payment information, block 1501(FIG. 15) of receiving, at a transaction system from a first entity, arequest including a merchant identifier associated with a merchant,block 1503 (FIG. 15) of sending the account identifier from thetransaction system to the first financial institution, block 1504 (FIG.15) of receiving, at the transaction system from the first financialinstitution, payment information regarding a payment to be made to thesecond account from the one or more first accounts, block 1505 (FIG. 15)of sending, from the transaction system to the second financialinstitution, the payment information, such that a point-of-sale terminalat the store of the merchant receives a notification of payment for thetransaction in real-time while the consumer remains at the store of themerchant, block 2401 (FIG. 24) of receiving a transaction amount and apreauthorization code from a first entity, block 2403 (FIG. 24) ofsending an approval for the transaction to the first entity in real-timewhile the user remains at the point-of-sale terminal of the firstentity, block 2703 (FIG. 27) of receiving, from the first financialinstitution, a request including the identifier of the first entity,block 2705 (FIG. 27) of sending the account identifier of the secondaccount to the first financial institution, block 2706 (FIG. 27) ofreceiving, from the first financial institution, payment informationregarding a payment to be made to the second account from the firstaccount for the transaction, and/or block 2707 (FIG. 27) of sending thepayment information to the second financial institution, to cause thepoint-of-sale terminal to receive a notification in real-time while theuser remains at the point-of-sale terminal.

In some embodiments, account system 144 can at least partially performblock 302 (FIG. 3) of determining, at the first system, using themerchant account database, first information, block 1202 (FIG. 12) ofdetermining, at the transaction system, an account identifier of thesecond account based on the merchant public identifier using a merchantaccount database, block 1502 (FIG. 15) of determining, at thetransaction system, an account identifier of the second account of themerchant maintained by a second financial institution using a merchantaccount database, and/or block 2704 (FIG. 27) of determining an accountidentifier of a second account of the first entity maintained by thesecond financial institution based on the identifier of the firstentity.

In a number of embodiments, transaction system 145 can at leastpartially perform block 305 (FIG. 3) of storing the payment informationin the transaction database, block 1204 (FIG. 12) of receiving, at thetransaction system from the first financial institution, paymentinformation regarding a payment to be made to the second account fromthe first account, block 1205 (FIG. 12) of sending, from the transactionsystem to the second financial institution, the payment information,block 2706 (FIG. 27) of receiving, from the first financial institution,payment information regarding a payment to be made to the second accountfrom the first account for the transaction, and/or block 2707 (FIG. 27)of sending the payment information to the second financial institution,to cause the point-of-sale terminal to receive a notification inreal-time while the user remains at the point-of-sale terminal.

In some embodiments, account system 146 can at least partially performgenerating the transaction code and/or merchant security transactioncode.

In a number of embodiments, preauthorization system 147 can at leastpartially perform block 2402 (FIG. 24) of verifying the preauthorizationcode using the digital signature of the preauthorization code, block2701 (FIG. 27) of receiving, at a transaction system being situatedalong a proxy communication channel extending from a point-of-saleterminal of a first entity to a mobile wallet provider, an encryptedtransaction code, and/or block 2702 (FIG. 27) of sending the encryptedtransaction code through the proxy communication channel to the mobilewallet provider, to cause the mobile wallet provider to decrypt theencrypted transaction code and verify the preauthorization from theuser.

In many embodiments, proxy communication system 148 can at leastpartially perform transmitting the encrypted transaction code along theproxy communication channel.

Continuing with FIG. 1, as described above, financial institution 150can include one or more systems, such as communication system 152,account system 153, and/or proxy communication system 154. Financialinstitution 150 and the systems therein are merely exemplary and are notlimited to the embodiments presented herein. Financial institution 150can be employed in many different embodiments or examples notspecifically depicted or described herein. In some embodiments, certainelements, systems, or modules of financial institution 150 can performvarious procedures, processes, and/or acts. In other embodiments, theprocedures, processes, and/or acts can be performed by other suitableelements, systems, or modules.

In many embodiments, communication system 152 can at least partiallyperform block 601 (FIG. 6) of receiving, at a second financialinstitution from a first system, payment information regarding a paymentto be made to a second account of a merchant maintained by the secondfinancial institution from a first account of a consumer maintained by afirst financial institution to pay the merchant for one or more items tobe purchased from the merchant by the consumer for the payment amount,and/or block 603 (FIG. 6) of sending, from the second financialinstitution to the point-of-sale terminal, a notification to satisfy anexpectation of the merchant for payment from the consumer.

In various embodiments, account system 153 can at least partiallyperform block 602 (FIG. 6) of crediting the second account with thepayment amount.

In many embodiments, proxy communication system 154 can at leastpartially perform transmitting the encrypted transaction code along theproxy communication channel.

Continuing with FIG. 1, as described above, mobile wallet provider 160can include one or more systems, such as proxy communication system 161.Mobile wallet provider 160 and the systems therein are merely exemplaryand are not limited to the embodiments presented herein. Mobile walletprovider 160 can be employed in many different embodiments or examplesnot specifically depicted or described herein. In some embodiments,certain elements, systems, or modules of mobile wallet provider canperform various procedures, processes, and/or acts. In otherembodiments, the procedures, processes, and/or acts can be performed byother suitable elements, systems, or modules.

In many embodiments, proxy communication system 161 can at leastpartially perform decrypting the encrypted transaction code, and/orverifying the preauthorization from the user.

Turning ahead in the drawings, FIG. 7 illustrates a computer 700, all ofwhich or a portion of which can be suitable for implementing anembodiment of at least a portion of point-of-sale terminal 110 (FIG. 1),mobile device 120 (FIG. 1), financial institution 130 (FIG. 1),transaction system 140 (FIG. 1), financial institution 150 (FIG. 1),and/or the techniques described in method 200 (FIG. 2), method 300 (FIG.3), method 400 (FIG. 4), method 500 (FIG. 5), method 600 (FIG. 6),method 900 (FIG. 9), method 1000 (FIG. 10), method 1100 (FIG. 11),method 1200 (FIG. 12), method 1300 (FIG. 13), method 1400 (FIG. 14),method 1500 (FIG. 15), and/or method 1600 (FIG. 16). Computer 700includes a chassis 702 containing one or more circuit boards (notshown), a USB (universal serial bus) port 712, a Compact Disc Read-OnlyMemory (CD-ROM) and/or Digital Video Disc (DVD) drive 716, and a harddrive 714. A representative block diagram of the elements included onthe circuit boards inside chassis 702 is shown in FIG. 8. A centralprocessing unit (CPU) 810 in FIG. 8 is coupled to a system bus 814 inFIG. 8. In various embodiments, the architecture of CPU 810 can becompliant with any of a variety of commercially distributed architecturefamilies.

Continuing with FIG. 8, system bus 814 also is coupled to memory 808that includes both read only memory (ROM) and random access memory(RAM). Non-volatile portions of memory storage unit 808 or the ROM canbe encoded with a boot code sequence suitable for restoring computer 700(FIG. 7) to a functional state after a system reset. In addition, memory808 can include microcode such as a Basic Input-Output System (BIOS). Insome examples, the one or more memory storage units of the variousembodiments disclosed herein can comprise memory storage unit 808, aUSB-equipped electronic device, such as, an external memory storage unit(not shown) coupled to universal serial bus (USB) port 712 (FIGS. 7-8),hard drive 714 (FIGS. 7-8), and/or CD-ROM or DVD drive 716 (FIGS. 7-8).In the same or different examples, the one or more memory storage unitsof the various embodiments disclosed herein can comprise an operatingsystem, which can be a software program that manages the hardware andsoftware resources of a computer and/or a computer network. Theoperating system can perform basic tasks such as, for example,controlling and allocating memory, prioritizing the processing ofinstructions, controlling input and output devices, facilitatingnetworking, and managing files. Some examples of common operatingsystems can comprise Microsoft® Windows® operating system (OS), Mac® OS,UNIX® OS, and Linux® OS.

As used herein, “processor” and/or “processing module” means any type ofcomputational circuit, such as but not limited to a microprocessor, amicrocontroller, a controller, a complex instruction set computing(CISC) microprocessor, a reduced instruction set computing (RISC)microprocessor, a very long instruction word (VLIW) microprocessor, agraphics processor, a digital signal processor, or any other type ofprocessor or processing circuit capable of performing the desiredfunctions. In some examples, the one or more processors of the variousembodiments disclosed herein can comprise CPU 810.

In the depicted embodiment of FIG. 8, various I/O devices such as a diskcontroller 804, a graphics adapter 824, a video controller 802, akeyboard adapter 826, a mouse adapter 806, a network adapter 820, andother I/O devices 822 can be coupled to system bus 814. Keyboard adapter826 and mouse adapter 806 are coupled to a keyboard 704 (FIGS. 7 and 8)and a mouse 710 (FIGS. 7 and 8), respectively, of computer 700 (FIG. 7).While graphics adapter 824 and video controller 802 are indicated asdistinct units in FIG. 8, video controller 802 can be integrated intographics adapter 824, or vice versa in other embodiments. Videocontroller 802 is suitable for refreshing a monitor 706 (FIGS. 7 and 8)to display images on a screen 708 (FIG. 7) of computer 700 (FIG. 7).Disk controller 804 can control hard drive 714 (FIGS. 7 and 8), USB port712 (FIGS. 7 and 8), and CD-ROM or DVD drive 716 (FIGS. 7 and 8). Inother embodiments, distinct units can be used to control each of thesedevices separately.

In some embodiments, network adapter 820 can comprise and/or beimplemented as a WNIC (wireless network interface controller) card (notshown) plugged or coupled to an expansion port (not shown) in computersystem 700 (FIG. 7). In other embodiments, the WNIC card can be awireless network card built into computer system 700 (FIG. 7). Awireless network adapter can be built into computer system 700 (FIG. 7)by having wireless communication capabilities integrated into themotherboard chipset (not shown), or implemented via one or morededicated wireless communication chips (not shown), connected through aPCI (peripheral component interconnector) or a PCI express bus ofcomputer system 700 (FIG. 7) or USB port 712 (FIG. 7). In otherembodiments, network adapter 820 can comprise and/or be implemented as awired network interface controller card (not shown).

Although many other components of computer 700 (FIG. 7) are not shown,such components and their interconnection are well known to those ofordinary skill in the art. Accordingly, further details concerning theconstruction and composition of computer 700 and the circuit boardsinside chassis 702 (FIG. 7) need not be discussed herein.

When computer 700 in FIG. 7 is running, program instructions stored on aUSB drive in USB port 712, on a CD-ROM or DVD in CD-ROM and/or DVD drive716, on hard drive 714, or in memory 808 (FIG. 8) are executed by CPU810 (FIG. 8). A portion of the program instructions, stored on thesedevices, can be suitable for carrying out all or at least part of thetechniques described herein. In various embodiments, computer 700 can bereprogrammed with one or more modules, applications, and/or databases toconvert a general purpose computer to a special purpose computer.

Although computer system 700 is illustrated as a desktop computer inFIG. 7, there can be examples where computer system 700 may take adifferent form factor while still having functional elements similar tothose described for computer system 700. In some embodiments, computersystem 700 may comprise a single computer, a single server, or a clusteror collection of computers or servers, or a cloud of computers orservers. Typically, a cluster or collection of servers can be used whenthe demand on computer system 700 exceeds the reasonable capability of asingle server or computer. In certain embodiments, computer system 700may comprise a portable computer, such as a laptop computer. In certainother embodiments, computer system 700 may comprise a mobile device,such as a smartphone. For example, mobile device 120 (FIG. 1) can be amobile device, such as a smartphone. In certain additional embodiments,computer system 700 may comprise an embedded system.

Although secure real-time payment transactions have been described withreference to specific embodiments, it will be understood by thoseskilled in the art that various changes may be made without departingfrom the spirit or scope of the disclosure. Accordingly, the disclosureof embodiments is intended to be illustrative of the scope of thedisclosure and is not intended to be limiting. It is intended that thescope of the disclosure shall be limited only to the extent required bythe appended claims. For example, to one of ordinary skill in the art,it will be readily apparent that any element of FIGS. 1-28 may bemodified, and that the foregoing discussion of certain of theseembodiments does not necessarily represent a complete description of allpossible embodiments. For example, one or more of the procedures,processes, or activities of FIGS. 2-6, 9-14, and/or 23-28 may includedifferent procedures, processes, and/or activities and be performed bymany different modules, in many different orders, and/or one or more ofthe procedures, processes, or activities of FIGS. 2-6, 9-14, and/or23-28 may include one or more of the procedures, processes, oractivities of another different one of FIGS. 2-6, 9-14, and/or 23-28.

Replacement of one or more claimed elements constitutes reconstructionand not repair. Additionally, benefits, other advantages, and solutionsto problems have been described with regard to specific embodiments. Thebenefits, advantages, solutions to problems, and any element or elementsthat may cause any benefit, advantage, or solution to occur or becomemore pronounced, however, are not to be construed as critical, required,or essential features or elements of any or all of the claims, unlesssuch benefits, advantages, solutions, or elements are stated in suchclaim.

Moreover, embodiments and limitations disclosed herein are not dedicatedto the public under the doctrine of dedication if the embodiments and/orlimitations: (1) are not expressly claimed in the claims; and (2) are orare potentially equivalents of express elements and/or limitations inthe claims under the doctrine of equivalents.

What is claimed is:
 1. A system comprising: one or more processors; andone or more non-transitory computer-readable media storing computinginstructions configured to run on the one more processors and perform:receiving a transaction amount and a preauthorization code from a firstentity, wherein the preauthorization code comprises a preauthorizationamount, an expiration time, and a digital signature, the transactionamount is for a transaction authorized by a user of a mobile device at apoint-of-sale terminal of the first entity, the transaction amount isless than or equal to the preauthorization amount, the mobile devicereceived the preauthorization code and stored the preauthorization codein the mobile device while the mobile device was in data communicationwith a mobile wallet provider, the mobile device provided a transactioncode to the point-of-sale terminal while the mobile device was unable tocommunicate with the mobile wallet provider, and the transaction codecomprises the preauthorization code, a transaction identifier for thetransaction, and the transaction amount; verifying the preauthorizationcode using the digital signature of the preauthorization code; andsending an approval for the transaction to the first entity in real-timewhile the user remains at the point-of-sale terminal of the firstentity.
 2. The system of claim 1, wherein the transaction code isprovided from the mobile device to the point-of-sale terminal by: themobile device displaying the transaction code as a matrix barcode on ascreen of the mobile device; and the point-of-sale terminal scanning thematrix barcode from the screen of the mobile device.
 3. The system ofclaim 1, wherein the transaction code is provided from the mobile deviceto the point-of-sale terminal by: the mobile device transmitting thetransaction code from the mobile device to the point-of-sale terminalusing a proximity-based wireless data communication protocol.
 4. Thesystem of claim 1, wherein the approval comprises one of: (a) asettlement credit push of funds for the transaction amount from a firstaccount of the user to a second account of the first entity, or (b) anirrevocable promise to pay the transaction amount from the first accountto the second account.
 5. The system of claim 1, wherein verifying thepreauthorization code further comprises: verifying that the transactionamount is less than or equal to the preauthorization amount; andverifying that the expiration time is at a future time.
 6. The system ofclaim 1, wherein the digital signature of the preauthorization code iscryptographically signed by a first financial institution that maintainsa first account of the user.
 7. The system of claim 1, wherein thetransaction amount and the preauthorization code is sent to atransaction system from the first entity through a second financialinstitution that maintains a second account of the first entity.
 8. Thesystem of claim 1, wherein the transaction is for a purchase by the userof one or more items from the first entity.
 9. The system of claim 1,wherein the mobile wallet provider is operated by a first financialinstitution that maintains a first account of the user.
 10. The systemof claim 1, wherein the preauthorization code is stored in the mobiledevice in an encrypted form.
 11. A method being implemented viaexecution of computing instructions configured to run at one or moreprocessors and stored at one or more non-transitory computer-readablemedia, the method comprising: receiving a transaction amount and apreauthorization code from a first entity, wherein the preauthorizationcode comprises a preauthorization amount, an expiration time, and adigital signature, the transaction amount is for a transactionauthorized by a user of a mobile device at a point-of-sale terminal ofthe first entity, the transaction amount is less than or equal to thepreauthorization amount, the mobile device received the preauthorizationcode and stored the preauthorization code in the mobile device while themobile device was in data communication with a mobile wallet provider,the mobile device provided a transaction code to the point-of-saleterminal while the mobile device was unable to communicate with themobile wallet provider, and the transaction code comprises thepreauthorization code, a transaction identifier for the transaction, andthe transaction amount; verifying the preauthorization code using thedigital signature of the preauthorization code; and sending an approvalfor the transaction to the first entity in real-time while the userremains at the point-of-sale terminal of the first entity.
 12. Themethod of claim 11, wherein the transaction code is provided from themobile device to the point-of-sale terminal by: the mobile devicedisplaying the transaction code as a matrix barcode on a screen of themobile device; and the point-of-sale terminal scanning the matrixbarcode from the screen of the mobile device.
 13. The method of claim11, wherein the transaction code is provided from the mobile device tothe point-of-sale terminal by: the mobile device transmitting thetransaction code from the mobile device to the point-of-sale terminalusing a proximity-based wireless data communication protocol.
 14. Themethod of claim 11, wherein the approval comprises one of: (a) asettlement credit push of funds for the transaction amount from a firstaccount of the user to a second account of the first entity, or (b) anirrevocable promise to pay the transaction amount from the first accountto the second account.
 15. The method of claim 11, wherein verifying thepreauthorization code further comprises: verifying that the transactionamount is less than or equal to the preauthorization amount; andverifying that the expiration time is at a future time.
 16. The methodof claim 11, wherein the digital signature of the preauthorization codeis cryptographically signed by a first financial institution thatmaintains a first account of the user.
 17. The method of claim 11,wherein the transaction amount and the preauthorization code is sent toa transaction system from the first entity through a second financialinstitution that maintains a second account of the first entity.
 18. Themethod of claim 11, wherein the transaction is for a purchase by theuser of one or more items from the first entity.
 19. The method of claim11, wherein the mobile wallet provider is operated by a first financialinstitution that maintains a first account of the user.
 20. The methodof claim 11, wherein the preauthorization code is stored in the mobiledevice in an encrypted form.